DEVICE, METHOD, AND GRAPHICAL USER INTERFACE FOR INTERACTING WITH USER INTERFACE OBJECTS RELATED TO AN APPLICATION - Patent application

Abstract

To provide an efficient human-machine interface.SOLUTION: A device displays, at a first time, a first user interface that includes a placement location and is configured to spatially accommodate a plurality of user interface objects. At the first time, a first user interface object is displayed at the placement location. At a second time, the first user interface is displayed with a second user interface object at the placement location. The second user interface object is automatically selected for display based on a current context of the device at the second time. In response to detecting a gesture of a first type directed to the placement location, the second user interface object is replaced with a user interface object different from the plurality of user interface objects associated with the placement location.SELECTED DRAWING: None

Description

[Technical Field]

[0001] This application relates generally to electronic devices with touch-sensitive surfaces, including, but not limited to, electronic devices with touch-sensitive surfaces for displaying and interacting with user interface objects corresponding to applications. [Background 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 manipulate user interfaces on displays and objects therein. Exemplary user interface objects include digital images, video, text, icons, and control elements such as buttons and other graphics.

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

[0004] However, 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 perform one or more actions on the selected user interface objects is tedious and creates a significant cognitive burden for the user. In addition, these methods take longer than necessary, thereby wasting energy. The latter problem is particularly acute in battery-operated devices. Summary of the Invention

[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 type of inputs from a user, creating a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0006] The above-mentioned deficiencies and other problems associated with user interfaces for electronic devices having touch-sensitive surfaces are reduced or eliminated by devices of the present disclosure. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, a tablet computer, or a 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 "touch screen" 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 the memory for performing multiple functions. In some embodiments, a user interacts with the GUI primarily through stylus and / or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functionality optionally includes image editing, drawing, presenting, word processing, spreadsheet creation, game playing, making phone calls, video conferencing, emailing, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note taking, and / or digital video playback, and executable instructions to perform those functionality are optionally contained on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

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

[0008] According to some embodiments, a method is performed on an electronic device including a display generation component and one or more input devices. The method includes displaying a first page of a multi-page home screen user interface, the first page of the multi-page home screen user interface including 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 satisfying first criteria while displaying the first page of the multi-page home screen user interface, and in response to detecting the first input satisfying the first criteria, displaying the first page of the multi-page home screen user interface in a first reconfiguration mode associated with the multi-page home screen user interface, wherein positions of the application icons within the first subset of application icons are adjustable in response to the user input detected during the first reconfiguration mode. The method further includes detecting a second input satisfying a second criterion while displaying a first page of the multi-page home screen user interface in the first reconfiguration mode, and activating a second reconfiguration mode associated with the multi-page home screen user interface in response to detecting the second input, and simultaneously displaying within the first user interface representations of multiple pages of the multi-page home screen user interface including a first representation of the first page of the multi-page home screen user interface and a second representation of a second page of the multi-page home screen user interface that is a second page different from the first page of the multi-page home screen user interface.

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

[0010] According to some embodiments, a 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 at a first time, 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 the first application and a second user interface object corresponding to a second application different from the first application, the first user interface object being displayed at the placement location. The method further includes displaying the first user interface at a second time after the first time with the 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 a current context of the device at 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 the placement location, replacing 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 accordance with a determination that the gesture is a first type of gesture.

[0011] According to some embodiments, a method is performed on an electronic device including a display generation component and one or more input devices. The method includes displaying a first user interface including a first 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 including information from the first application, a second user interface object including information from a second application different from the first application, and a third user interface object including information from a third application different from the first and second applications. The method further includes detecting an occurrence of a distinct condition after displaying the first user interface object corresponding to the first application at the first location within the first user interface. The method further includes displaying a second user interface object at the first location within the first user interface in response to detecting the occurrence of the distinct condition. The method further includes, after displaying the second user interface object at the first placement location within the first user interface, displaying a configuration user interface corresponding to the first placement location, wherein displaying the configuration user interface includes simultaneously displaying at least a portion of a first representation of the first user interface object and at least a portion of a second representation of the second user interface object. The method further includes, while displaying the configuration user interface corresponding to the first placement location, detecting a first user input directed at a respective portion of the configuration user interface.The method further includes, in response to detecting a first user input directed at a respective portion of the configuration user interface, in accordance with determining that the first user input satisfies the selection criteria when directed at a first representation of a first user interface object of the plurality of user interface objects shown in the configuration user interface, and that the first user input includes a movement that satisfies the first movement criterion, ceasing to display the configuration user interface corresponding to the first placement position in accordance with the movement 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 movement of the first user input, the second user interface being different from the configuration user interface, and the second placement position being different from the first placement position.

[0012] According to some embodiments, a 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 multi-page home screen user interface in a first reconfiguration mode, wherein individual positions of a first plurality of application icons within the first page of the multi-page home screen user interface are adjustable according to user input in the first reconfiguration mode. The method further includes detecting, while displaying the first page of the multi-page home screen user interface in the first reconfiguration mode, a first input corresponding to a request to enter a second reconfiguration mode from the first reconfiguration mode, wherein availability of one or more pages within the multi-page home screen user interface can be changed according to the user input in the second reconfiguration mode. The method further includes, in response to detecting the first input, replacing the display of the first page of the multi-page home screen user interface in the first reconfiguration mode with a display of individual representations of at least two pages of the multiple pages of the multi-page home screen user interface in a second reconfiguration mode, the individual representations including at least a first representation of the first page of the multi-page home screen user interface and a second representation of a second page of the multi-page home screen user interface that is different from the first page of the multi-page home screen user interface. The method further includes detecting a second input while displaying the individual representations of at least two pages of the multiple pages of the multi-page home screen user interface in the second reconfiguration mode, the individual representations including the first representation of the first page and the second representation of the second page. The method further includes, in response to detecting a second input, the second input being directed to a second representation of the second page displayed in the second reconfiguration mode, and displaying the second page of the multi-page home screen user interface in the first reconfiguration mode in accordance with a determination that the second input satisfies a first criterion, wherein individual positions of the second plurality of application icons within the second page of the multi-page home screen user interface are adjustable in accordance with the user input in the first reconfiguration mode.

[0013] According to some embodiments, a method is performed on an electronic device including a display generation component and one or more input devices. The method includes displaying a respective page of a home screen user interface, the respective page of the home screen user interface including 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, into the respective page of the home screen user interface, a first user interface object including a plurality of application icons for a plurality of applications automatically selected by the computer system. The method further includes, in response to detecting the series of one or more inputs, simultaneously displaying, on the respective page of the home screen user interface, two or more of the first plurality of application icons in the first predetermined arrangement and a second plurality of application icons different from the first plurality of application icons, wherein the second plurality of application icons are automatically arranged on the respective 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 respective page of the home screen user interface, and the second plurality of application icons are automatically selected by the computer system for inclusion on the respective page of the home screen user interface.

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

[0015] According to some embodiments, a method is performed on an electronic device including a display generation component and one or more input devices. The method includes displaying, via the display generation component, a first user interface for selecting a user interface object for placement on a home screen user interface of a computer system, the first user interface including a first user interface object including first application content corresponding to a first application. The method further includes detecting a first user input directed to a distinct location within the first user interface while displaying the first user interface. In response to detecting the first user input directed to the distinct 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 configuration options different from the one or more predetermined configuration options in accordance with a determination that the distinct location n corresponds to a location of a first user interface object including application content corresponding to the first application and pre-configured with one or more predetermined configuration options corresponding to the first user interface object, and that the first user input is a first type of input. The method further includes, in response to detecting a first user input directed at a distinct location within the first user interface, displaying the first user interface object including application content corresponding to the first application in a distinct user interface different from the first user interface in accordance with a determination that the distinct location corresponds to a location of a first user interface object including application content corresponding to the first application and that the first user input is a second type of input different from the first type of input, with one or more predetermined configuration options corresponding to the first user interface object.

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

[0017] Thus, electronic devices having a display generating component, a touch-sensitive surface, optionally one or more sensors that detect the intensity of contact with the touch-sensitive surface, optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system are provided with improved methods and interfaces for navigating through user interfaces and interacting with control objects, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices. [Brief explanation of the drawings]

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

[0019] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

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

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

[0022] [Figure 2]1 illustrates a portable multifunction device with a touch screen according to some embodiments.

[0023] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0024] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0025] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display in accordance with some embodiments.

[0026] [Figure 4C] 1 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 4D] 1 illustrates an example of a dynamic intensity threshold, according to some embodiments. [Figure 4E] 1 illustrates an example of a dynamic intensity threshold, according to some embodiments.

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

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

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

[0030] [Figure 5D1] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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]1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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]1 illustrates an exemplary user interface for selecting to view and update user interface objects including application content (e.g., mini-application objects, widgets, etc.) associated with placement positions 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] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E2] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E3] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E4] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E5] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E6] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E7] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E8] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E9] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E10] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E11] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E12] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E13] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E14] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E15]1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E16] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E17] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E18] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E19] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E20]1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E21] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E22] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E23] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E24] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E25]1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E26] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E27] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E28] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E29] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E30]1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E31] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments. [Figure 5E32] 1 illustrates an exemplary user interface for interacting with a user interface object (e.g., a widget or mini-application object stack, etc.) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface, etc.) in accordance with some embodiments.

[0032] [Figure 5F1] 1 illustrates 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) according to some embodiments. [Figure 5F2] 1 illustrates 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) according to some embodiments. [Figure 5F3] 1 illustrates 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) according to some embodiments. [Figure 5F4] 1 illustrates 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) according to some embodiments. [Figure 5F5] 1 illustrates 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) according to some embodiments. [Figure 5F6] 1 illustrates 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) according to some embodiments. [Figure 5F7] 1 illustrates 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) according to some embodiments. [Figure 5F8] 1 illustrates 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) according to some embodiments. [Figure 5F9] 1 illustrates 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) according to some embodiments. [Figure 5F10] 1 illustrates 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) according to some embodiments. [Figure 5F11]1 illustrates 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) according to some embodiments. [Figure 5F12] 1 illustrates 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) according to some embodiments. [Figure 5F13] 1 illustrates 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) according to some embodiments. [Figure 5F14] 1 illustrates 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) according to some embodiments. [Figure 5F15] 1 illustrates 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) according to some embodiments. [Figure 5F16] 1 illustrates 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) according to some embodiments. [Figure 5F17] 1 illustrates 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) according to some embodiments. [Figure 5F18]1 illustrates 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) according to some embodiments. [Figure 5F19] 1 illustrates 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) according to some embodiments. [Figure 5F20] 1 illustrates 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) according to some embodiments. [Figure 5F21] 1 illustrates 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) according to some embodiments. [Figure 5F22] 1 illustrates 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) according to some embodiments. [Figure 5F23] 1 illustrates 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) according to some embodiments. [Figure 5F24] 1 illustrates 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) according to some embodiments. [Figure 5F25]1 illustrates 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) according to some embodiments. [Figure 5F26] 1 illustrates 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) according to some embodiments. [Figure 5F27] 1 illustrates 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) according to some embodiments. [Figure 5F28] 1 illustrates 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) according to some embodiments. [Figure 5F29] 1 illustrates 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) according to some embodiments. [Figure 5F30] 1 illustrates 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) according to some embodiments.

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

[0034] [Figure 5H1] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H2]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H3] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H4] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H5] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H6]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H7] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H8] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H9] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H10]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H11] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H12] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H13] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H14]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H15] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H16] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H17] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H18]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H19] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H20] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H21] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H22]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H23] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H24] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H25] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H26]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H27] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H28] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H29] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H30]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H31] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H32] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H33] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H34]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H35] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H36] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H37] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H38]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H39] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H40] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H41] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H42]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H43] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H44] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H45] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H46]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H47] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H48] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H49] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H50]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H51] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H52] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H53] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H54]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H55] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H56] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H57] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H58]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H59] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H60] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H61] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H62]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H63] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H64] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H65] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H66]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H67] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H68] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H69] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H70]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H71] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H72] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H73] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H74]FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H75] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 5H76] FIG. 1 illustrates various ways in which 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments.

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

[0036] [Figure 6A] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6B] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6C] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6D] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6E] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6F] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6G] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6H] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6I] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6J] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments. [Figure 6K] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with user interface objects corresponding to different applications according to some embodiments.

[0037] [Figure 7A] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7B] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7C] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7D] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7E] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7F] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7G] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments. [Figure 7H] FIG. 10 is a flow diagram illustrating a method for configuring a multi-page home screen user interface according to some embodiments.

[0038] [Figure 8A] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8B] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8C] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8D]1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8E] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8F] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8G] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8H] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8I] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8J] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8K]1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8L] 1 is a flow diagram illustrating a method 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 according to some embodiments. [Figure 8M] 1 is a flow diagram illustrating a method 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 according to some embodiments.

[0039] [Figure 9A] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9B] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9C] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9D]FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9E] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9F] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9G] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments. [Figure 9H] FIG. 10 is a flow diagram illustrating a selection method for displaying and updating user interface objects (e.g., mini-application objects, widgets, etc.) associated with a placement location within a page of a home screen user interface, according to some embodiments.

[0040] [Figure 10A] FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10B]FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10C] FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10D] FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10E] FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10F] FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10G]FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments. [Figure 10H] FIG. 1 is a flow diagram illustrating a method of interacting with a user interface object (e.g., a widget or mini-application object stack) that includes multiple application contents associated with a common placement location (e.g., on a page of a home screen user interface and within a stack-specific configuration user interface), according to some embodiments.

[0041] [Figure 11A] FIG. 10 is a flow diagram illustrating a method of 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) according to some embodiments. [Figure 11B] FIG. 10 is a flow diagram illustrating a method of 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) according to some embodiments. [Figure 11C] FIG. 10 is a flow diagram illustrating a method of 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) according to some embodiments. [Figure 11D] FIG. 10 is a flow diagram illustrating a method of 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) according to some embodiments.

[0042] [Figure 12A]FIG. 1 is a flow diagram illustrating a method for displaying and interacting with a user interface object (e.g., a suggested applications widget, a recommended applications widget, a recent apps widget, etc.) that presents application icons automatically selected by a computer system at a user-selected location (e.g., a user-selected placement location on a page of a home screen user interface, on a widget screen, etc.), according to some embodiments. [Figure 12B] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with a user interface object (e.g., a suggested applications widget, a recommended applications widget, a recent apps widget, etc.) that presents application icons automatically selected by a computer system at a user-selected location (e.g., a user-selected placement location on a page of a home screen user interface, on a widget screen, etc.), according to some embodiments. [Figure 12C] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with a user interface object (e.g., a suggested applications widget, a recommended applications widget, a recent apps widget, etc.) that presents application icons automatically selected by a computer system at a user-selected location (e.g., a user-selected placement location on a page of a home screen user interface, on a widget screen, etc.), according to some embodiments. [Figure 12D] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with a user interface object (e.g., a suggested applications widget, a recommended applications widget, a recent apps widget, etc.) that presents application icons automatically selected by a computer system at a user-selected location (e.g., a user-selected placement location on a page of a home screen user interface, on a widget screen, etc.), according to some embodiments. [Figure 12E]FIG. 1 is a flow diagram illustrating a method for displaying and interacting with a user interface object (e.g., a suggested applications widget, a recommended applications widget, a recent apps widget, etc.) that presents application icons automatically selected by a computer system at a user-selected location (e.g., a user-selected placement location on a page of a home screen user interface, on a widget screen, etc.), according to some embodiments. [Figure 12F] FIG. 1 is a flow diagram illustrating a method for displaying and interacting with a user interface object (e.g., a suggested applications widget, a recommended applications widget, a recent apps widget, etc.) that presents application icons automatically selected by a computer system at a user-selected location (e.g., a user-selected placement location on a page of a home screen user interface, on a widget screen, etc.), according to some embodiments.

[0043] [Figure 13A] FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13B] FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13C]FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13D] FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13E] FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13F] FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13G]FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments. [Figure 13H] FIG. 10 is a flow diagram illustrating a method for 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 (e.g., in response to rearranging, deleting, adding, passing through, removing one or more user interface objects corresponding to different applications), according to some embodiments.

[0044] [Figure 14A] FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. [Figure 14B] FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. [Figure 14C] FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. [Figure 14D]FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. [Figure 14E] FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. [Figure 14F] FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. [Figure 14G] FIG. 1 is a flow diagram illustrating a method for constructing a user interface object containing application content (e.g., a widget, a mini-application object, etc.) and adding it to another user interface (e.g., a home screen page) in accordance with some embodiments. DETAILED DESCRIPTION OF THE INVENTION

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

[0046] The following embodiments provide additional system-configured page(s) of the home screen user interface that include application icons automatically categorized and arranged within automatically generated groupings. A user can easily navigate to the system-generated page(s) of the home screen and locate the application icon for a desired application based on characteristics (e.g., when installed, app store category, functionality, etc.) using the same navigation gestures used to navigate between user-configured 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-generated page(s) of the home screen user interface. In some embodiments, the system-generated home screen also includes user interface objects containing application content, also referred to as mini-application objects or widgets, that provide a limited subset of functionality and / or information available from their corresponding applications without the need to launch the applications. In some embodiments, the system configuration page(s) of the multi-page home screen user interface provide a search input area that allows a user to enter search criteria (e.g., keywords, filters such as recently notified apps, apps launched by a particular launcher, etc.) and returns applications corresponding to the search criteria as search results (e.g., installed applications and / or applications available from an app store, etc.).In some embodiments, search results include application icons that can be directly interacted with to, for example, launch the corresponding application, drag and drop to a desired location within the user-configured page of the home screen, and / or deleted from the device without the user having to locate the application icon in its current location on the user-configured page of the home screen user interface. In some embodiments, similar functionality is provided for application icons shown on the system-configured home screen. In some embodiments, system-generated groupings are represented on the system-configured page of the home screen user interface as large folder icons, with individual large folder icons corresponding to individual groupings and, when activated, displaying application icons (or copies of or links to them) for multiple (e.g., some or all) applications from the user-configured page of the home screen user interface specified for the individual grouping represented by the large folder icon. The representation of a system-generated grouping (e.g., large folder icon) optionally includes a folder launch icon and miniature versions of application icons corresponding to at least a subset of the applications included in the grouping (e.g., applications with unread notifications or badges, recently accessed applications, etc.). When an individual miniature application icon is activated (e.g., by a tap input, a double-tap input, etc.), the computer system launches the individual miniature application icon's corresponding application. When a folder launch icon is activated (e.g., by a tap input, a double-tap input, etc.), it displays the contents of a folder containing application icons corresponding to applications in the individual groupings. In some embodiments, the application icons and groupings included in the system configuration page of the multi-page home screen user interface are not changed by user input, or at least not in the same way that they can be changed (e.g., deleted, moved, etc.) within the user configuration page of the home screen user interface.In some embodiments, the system configuration page is presented as a page of the multi-page home screen user interface with a corresponding page indicator icon that indicates its normal location within the series of pages of the multi-page home screen user interface. In some embodiments, the system configuration page is presented as a user interface overlay or a separate user interface (e.g., an application library user interface) that does not have a corresponding page indicator icon among the page indicator icons of the user-configured pages of the multi-page home screen user interface. In some embodiments, regardless of its appearance, the system configuration page of the home screen user interface is accessed and displayed in response to the same types of page navigation inputs used to navigate between user-configured pages of the multi-page home screen user interface.

[0047] Some methods of configuring pages of a multi-page home screen user interface include users laboriously 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. There is also no easy way to arrange different pages of a multi-page home screen as a whole or to restore a page or a set of application icons after it has been deleted from the multi-page home screen user interface. As disclosed herein, a computer system provides a two-step process for invoking a page edit mode for a multi-page home screen user interface, where an icon reconfiguration mode is first invoked on an individual page of the multi-page home screen user interface, and while displaying the individual page of the multi-page home screen in the icon reconfiguration mode, user input is optionally detected to activate the page edit mode, which can hide, rearrange, and / or remove all pages of the multi-page home screen user interface from within the multi-page home screen user interface when the page edit mode is exited. In some embodiments, while in page edit mode, user input is optionally detected to move previously hidden pages from a preset hold area in the page edit user interface or mark them as unhidden, so that they reappear in the multi-page home screen user interface when exiting page edit mode. In some embodiments, while in page edit mode, a delete input is applied to multiple (e.g., all, some, etc.) hidden pages stored in a preset hold area. In some embodiments, hidden pages are not deleted and are easily restored in the future.In some embodiments, affordances for entering page editing mode from icon reconfiguration mode are displayed on multiple (e.g., some or all) pages (e.g., system-configured pages and / or user-configured pages) of the multi-page home screen user interface in icon reconfiguration mode, and optionally in positions 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 a 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 the insertion is possible, it may cause existing application icons on the user interface to reflow, sometimes pushing some icons at the bottom of a page onto the next page, which may cause a cascading effect that unnecessarily changes the layout on a multi-page home screen user interface. As disclosed herein, the computer system moves the set of application icons and / or widgets currently located in the desired placement location selected by the user for the new widget to a pre-defined location (e.g., a new folder or a 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 other portions of the current page or other existing pages of the multi-page home screen user interface. In some embodiments, when a new widget is dragged around a page before being inserted into the page, only the set of application icons at the new widget's current location are sent to individual locations, so that the user gets a preview of the final state of the page before committing to 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 the 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 into the desired placement location on the desired page of the home screen user interface.If there is sufficient space on the page of the home screen user interface, the application icons are displaced and shifted on the page to make room for the insertion of the new widget. In some embodiments, a quick action menu associated with the widget includes a size selector showing different available sizes for the widget, and using the size selection to select a different size for the widget resizes the widget and optionally causes other application icons and / or widgets to reflow on the same page of the home screen user interface. In some embodiments, in addition to reflowing 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, etc.). In some embodiments, resizing a widget optionally causes a rearrangement of the application icons and / or widgets on the page of the home screen user interface with respect to block sizes corresponding to the new and / or old size of the widget (and optionally the sizes and positions of other widgets on the same page).

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

[0050] Some methods of browsing a list of applications with available widgets and selecting a widget from the list to enter a fixed position in the widget screen are strict and cumbersome. It is difficult for users to find a useful widget and find an easy opportunity to add the widget to a desired location on a page of a home screen user interface. As disclosed herein, a widget stack includes multiple widgets that are displayed at different times in the same placement position. A stack-specific configuration user interface includes a representation of multiple widgets (e.g., some or all, respectively) in a widget stack. In addition to providing configuration options and entry points for additional configuration options for widgets in a stack, the stack-specific configuration user interface also serves dual purpose, providing widget selection and configuration user interface functionality for widgets in the stack, and adding one or more widgets to a default or user-selected location in response to selecting one or more widgets, followed by input corresponding to a request to add the widget 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 at a desired location within a page of the home screen user interface). In some embodiments, dragging a widget from a stack-specific configuration user interface removes the widget from the stack (e.g., adding it to another user-selected location, or optionally without adding it to another location). In some embodiments, the representations of widgets in the stack-specific widget configuration user interface are reordered in response to user input, resulting in a reordering of the widgets in the stack. In some embodiments, the representations of widgets in the stack-specific widget configuration user interface include scaled-down images of the widgets and current application data.In some embodiments, the representation visually indicates what information within the widget contributes to the automatic selection of the widget as the currently displayed widget in its placement position in the widget stack.

[0051] Some methods of providing an entry point into a page edit mode, which allows a user to manage or delete an entire page of application icons within a home screen user interface, do not involve first initiating the icon reconfiguration mode and entering the page edit mode while in the icon reconfiguration mode. Some methods of providing a page edit mode also do not provide an entry point into the icon reconfiguration mode. Essentially, page edit and icon reconfiguration are separated from each other in some computer systems, and transitioning from one mode to the other involves multiple user inputs, making the process cumbersome and time-consuming. As disclosed herein, a computer system provides an entry point into the icon reconfiguration mode from the page edit mode and an entry point into the icon reconfiguration mode from the page edit mode. Specifically, the computer system enters the page edit mode in response to a user input detected while a first page of the home screen user interface is displayed in the icon reconfiguration mode, and exits the page edit mode to display another page of the home screen user interface displayed in the icon reconfiguration mode in response to an input directed to a representation of the other page. The ability to transition back and forth between the page edit mode and the 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-arranged pages of the home screen user interface, optionally including both hidden pages and currently available pages in the same order according to their original order before some of the pages were hidden. In some embodiments, the order of pages, including hidden pages, is reordered in the home screen user interface by reordering representations of pages, including representations of hidden pages, in the page editing user interface. In some embodiments, the layout and scaling of the representations of pages in 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 there is more than a preset number of pages in the home screen user interface, the fixed size page editing user interface will be a single scrollable page or will contain multiple pages.

[0052] On some computer systems, a small number of user-selected application icons may be included in a widget and placed on a page of a home screen user interface. 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 extensive effort to maintain its usefulness. In addition, the widget 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 preset configuration of the home screen user interface. As disclosed herein, a computer system provides a suggested application widget that includes application icons for multiple applications that are automatically selected by the computer system based on criteria for measuring the application's likely relevance to the user, taking into account the current context. The suggested application widget is rearrangeable by the user during an icon reconfiguration mode and can be inserted into a user-specified position on a page of the home screen user interface. When displaying the suggested application widget, the computer system displays application icons within the suggested application widget that have sizes and positions that match and are aligned with other application icons on the same page, creating a uniform and consistent layout even when the suggested application widget is displayed in different user-selected placement positions on the page.In some embodiments, the suggested application widget acts as a mini-application library, providing a convenient opportunity for a user to find a desired application icon among the currently displayed application icons in the suggested application widget, select the currently displayed application icon in the suggested application widget, and drag it to another position on the same page or a different page of the home screen user interface to add the application icon at the user-selected position (optionally, the select and drag input, and / or the drop input triggers an icon reconfiguration mode). In some embodiments, the drag and drop functionality described above is available only when the page is in the icon reconfiguration mode. In some embodiments, the border and background of the suggested application widget are visually suppressed when the page is displayed in normal mode and become more apparent when the page enters the icon reconfiguration mode. In some embodiments, the suggested application widget behaves similarly to other application icons and widgets in that, in response to a pre-configured input for triggering the display of a quick action menu for a user interface object corresponding to the application, the computer system also displays a quick action menu for the suggested application widget. The quick action menu of a suggested application widget includes widget-specific options for the suggested application widget and, optionally, application-specific options corresponding to an application icon in the suggested application widget if the location of the input corresponds to that application icon. In some embodiments, the application-specific options for an application include an option to hide the application in the suggested application widget (e.g., temporarily, permanently, on the current page, on another page, etc.).As disclosed herein, with alignment between application icons that include a suggested application widget and other application icons on the same page, when the suggested application widget is displayed at different user locations and different sets of application icons are presented within user-selected locations, the page that includes the suggested application widget maintains an orderly, organized arrangement, such that the user is less likely to become confused when placing a desired application icon on the page and / or is less likely to experience issues with reflowing the application icons on the page when the configuration of the page is altered by subsequent changes (e.g., adding, removing, and rearranging application icons and widgets according to additional user input). This feature enhances device usability (e.g., by allowing the user to select placement locations for automatically selected application icons while maintaining an organized layout on the page at user-selected locations), 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 assisting the user in using the device more quickly and efficiently).

[0053] On some computer systems, application icons on a home screen user interface may be positioned arbitrarily according to user input, or 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, the application icons are reflowed sequentially according to a predetermined order. However, these reflow methods do not consider the impact 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 were allowed, the page could 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 continuous reflow of objects that are all the same size is not suitable for pages containing objects of various sizes, and simply continuing the same reflow method would result in chaos and an incorrectly ended up layout of the page. 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 relative to one or more pages. In some embodiments, the rules are implemented to avoid one or more configurations of the pages that are likely to result in a concentration of alignment issues and / or that are likely to contribute to page disorganization and user confusion over time.In some embodiments, when user interface objects containing application content are inserted into a page, rules are implemented to provide visual feedback about how the page will be organized (e.g., via automatic organization into blocks, reflow and movement as blocks, etc.) before user input is completed and the user interface objects containing application content are actually inserted into the page, and / or before user input has selected any particular placement location for the user interface objects containing application content on the page. In some embodiments, rules are implemented to provide visual feedback about preferred and / or required placement locations within the page as soon as the user interface objects containing application content are dragged onto the page, so that the user is aware of such recommendations or restrictions regarding placement locations without failing by attempting to drop the user interface objects at disallowed placement locations. These features enhance device usability (e.g., by providing the user with preferred visual feedback and guidance when the user provides input to reorganize 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 device's battery life (e.g., by assisting the user to 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 shows a list of applications with available widgets or from dedicated applications for creating specific types of customized widgets (e.g., an application for creating a home screen widget for a weather forecast, an application for creating a widget for saving bookmarks, etc.). These methods do not provide a preview of multiple pre-configured widgets corresponding to different applications within the same user interface, nor do they provide easy access to both configuration options for modifying pre-configured widgets and inserting widgets as pre-configured in 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, the widget selection and configuration user interface acts as a mini-library of pre-configured widgets and / or widget stacks, but also allows access to widget-specific configuration options for pre-configured widgets and / or widget stacks. The widget selection and configuration user interface and the widget-specific configuration user interface optionally display widgets with currently selected configuration options and real-time data from the widget(s) corresponding to the application(s).A widget selection and configuration user interface that performs the combined functions of allowing a user to view pre-configured widgets, providing access to configuration options for the widgets, and allowing a user to select and insert / move one or more widgets to another user-selected location from the widget selection and configuration user interface or a widget-specific configuration user interface, improves and enhances the usability of the device (e.g., by making it easier to discover widgets and add them to different locations), the interface between the user and the device is more efficient (e.g., by helping the user achieve intended results with the necessary inputs and reducing user errors when operating / interacting with the device), and improves the battery life of the device (e.g., by helping the user use the device more quickly and efficiently).

[0055] 1A-1C, 2, and 3 provide a description of an exemplary device. 4A-4B, as well as FIGS. 5A1-5A36, 5B1-5B19, 5C1-5C73, 5D1-5D12, 5E1-5E32, 5F1-5F30, 5G1-5G31, 5H1-5H76, and 5I1-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, exemplary user interfaces for reconfiguring a multi-page home screen user interface, exemplary user interfaces for inserting user interface objects including application content (e.g., mini-application objects, widgets, etc.) into pages of a home screen user interface (e.g., a single-page or multi-page home screen user interface), and exemplary user interfaces for inserting application content (e.g., mini-application objects, widgets, etc.) into pages of a home screen user interface (e.g., a single-page or multi-page home screen user interface), according to some embodiments. 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., widget 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 a 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 presenting application icons automatically selected by the computer system at user-selected locations; and an exemplary user interface for selecting to display and update 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.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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, or removing one or more user interface objects corresponding to different applications) and user interfaces for configuring and adding user interface objects containing application content (e.g., widgets, mini-application objects, etc.) to another user interface, according to some embodiments.

[0021] 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 may be moved and / or rearranged during a reconfiguration mode (e.g., in response to rearranging, deleting, adding, passing through, or removing one or more user interface objects corresponding to different applications) and user interfaces for configuring and adding user interface objects containing application content (e.g., widgets, mini-application objects, etc.) to another user interface, according to some embodiments. interacting with a plurality of user interface objects including application content associated with a placement location of the plurality of pages of a home screen user interface; displaying and interacting with a user interface object presenting an application icon automatically selected by the computer system at a user-selected location; existing user interface objects corresponding to different applications on a page of the home screen user interface being moved and / or repositioned during a reconfiguration mode; and configuring a user interface object including application content and adding it to another user interface. 4A to 4B, 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, and the user interfaces of FIGS. 6A to 6K, 7A to 7H, 8A to 8M, 9A to 9H, 10A to 10H,The processes shown in Figures 11A to 11D, 12A to 12F, 13A to 13H, and 14A to 14G are shown. Exemplary Devices

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

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

[0058] The terminology used in the description of the various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. In the description of the various embodiments set forth and in the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

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

[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, that also includes other functions, such as PDA and / or music player functions. 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 laptops 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 rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

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

[0062] The device typically supports a variety of applications such as one or more of a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

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

[0064] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112, according to some embodiments. Touch-sensitive display system 112 may conveniently be referred to as a "touch screen" or simply a touch-sensitive display. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input or control devices 116, and external port 124. Device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more intensity sensors 165 that detect the intensity of a contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0065] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.Using tactile output to provide haptic feedback to the user improves usability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate inputs and reducing user errors when operating / interacting with the device), as well as reducing power usage and improving 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 movement waveform of the tactile output, the frequency of the tactile output, and / or the duration of the tactile output.

[0067] When tactile outputs having different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a movable mass to generate the tactile output), the tactile outputs, in some circumstances, cause different tactile sensations when a user holds or touches the device. When a user's sensations are based on the user's perception of the tactile output, most users are able to distinguish changes in waveform, frequency, and amplitude of the tactile output generated by the device. Thus, the waveform, frequency, and amplitude can be adjusted to indicate to the user that different actions have been performed. Thus, in some situations, tactile output having a tactile output pattern designed, selected, and / or developed to simulate the properties (e.g., size, material, weight, stiffness, smoothness, etc.), behaviors (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 having virtual boundaries and virtual objects, an actual physical environment having physical boundaries and physical objects, and / or any combination of the above) provides useful feedback to a user that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, the tactile output is optionally generated to correspond to feedback unrelated to simulated physical properties, such as input thresholds or object selection. In some situations, such tactile output provides useful feedback to a user that reduces input errors and increases the efficiency of the user's operation of the device.

[0068] In some embodiments, a tactile output having a suitable tactile output pattern serves as a cue to the occurrence of an event of interest behind the scenes within a user interface or device. Examples of events of interest include activation of an affordance provided on the device or within the user interface (e.g., a real button, a virtual button, or a toggle switch), success or failure of a requested action, reaching or crossing a boundary within the user interface, entering a new state, switching input focus between objects, activating a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, a tactile output is provided to serve as a warning or alert of an impending event or outcome that will occur unless a redirection or interrupting input is detected in a timely manner. Tactile output is also used in other contexts to enhance the user experience, improve the accessibility of a 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. The tactile output, optionally accompanied by an audio output and / or a change in the visible user interface, further enhances the user's experience when interacting with the user interface and / or device, facilitates better communication of information about the state of the user interface and / or device, reduces input errors, and increases the efficiency of the user's operation of the device.

[0069] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in FIG. 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 other components of device 100, such as CPU(s) 120 and peripherals interface 118, is optionally controlled by memory controller 122.

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

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

[0073] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates wirelessly with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. Radio options include 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 (CDMA).Wireless technologies include, but are not limited to, standard 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), and Instant Messaging and Presence Services (IMP). The present invention may use any of a number of communication standards, protocols, and technologies, including, but not limited to, Intermediate Message Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

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

[0075] I / O subsystem 106 couples input / output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, light sensor controller 158, intensity sensor controller 159, 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 send electrical signals to other input or control devices 116. Other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, infrared port, USB port, stylus, and / or pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include up / down buttons for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2).

[0076] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives electrical signals from and / or sends electrical signals to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object configured to respond to input directed towards the graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selectable menu item, a switch, a hyperlink, or other user interface control.

[0077] Touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contacts (and any movement or breaking of contact) on touch-sensitive display system 112 and translate the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch-sensitive display system 112. In some embodiments, the point of contact between touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

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

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

[0080] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from 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 provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of electrical power within a portable device.

[0082] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor(s) 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor(s) 164 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), light sensor(s) 164 optionally capture still images and / or video. In some embodiments, the light sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touchscreen can be used as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is placed on the front of the device so that an image of the user is captured (e.g., for a selfie, for a video conference while the user is viewing other video conference participants on the touchscreen, etc.).

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

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

[0085] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to haptic feedback controller 161 in I / O subsystem 106. In some embodiments, tactile output generator(s) 167 include one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear movement, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Tactile output generator(s) 167 receive tactile feedback generation instructions from haptic feedback module 133 and generate tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

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

[0087] In some embodiments, software components stored in memory 102 include an operating system 126, a communications 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 applications (or instruction sets) 136. Additionally, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates which applications, views, or other information occupy various areas of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or location information regarding the device's position and / or orientation.

[0088] Operating system 126 (e.g., 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 facilitating communication between various hardware and software components.

[0089] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector identical to, similar to, and / or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector identical to, similar to, and / or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.

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

[0091] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of the detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture includes detecting a finger-down event, followed by detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event, followed by detecting one or more finger drag events, and then detecting a finger-up (lift-off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected with respect to a stylus by detecting particular contact patterns 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 is not related to the intensity of the finger contact between detecting the finger-down event and detecting the finger-up event. In some embodiments, a tap gesture is detected according to determining that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of the finger contact during the tap 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 the contact to meet a given intensity threshold for the particular input criteria to be met. For clarity, finger contacts in a tap gesture generally need to meet a nominal contact-detection intensity threshold below which the contact is not detected in order to detect a finger-down event. A similar analysis applies to detecting a stylus tap gesture or other contact. In cases where the device is capable of detecting contact of a finger or stylus hovering over the touch-sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0093] In a similar manner, the same concepts apply 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 included in the gesture or that do not require the contacts performing the gesture to reach an intensity threshold in order to be recognized. For example, a swipe gesture is detected based on the amount of movement of one or more contacts, a pinch gesture is detected based on the movement of two or more contacts toward each other, a de-pinch gesture is detected based on the movement of two or more contacts away from each other, and a long press gesture is detected based on the duration of contact on the touch-sensitive surface that is less than a threshold amount of movement. Thus, a statement that a particular gesture recognition criterion does not require the intensity of a contact(s) to meet a corresponding intensity threshold in order for the particular gesture recognition criterion to be met means that the particular gesture recognition criterion can be met when the contact(s) in the gesture do not reach the corresponding intensity threshold, and can also be met in situations where 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 a determination that a finger-down event and a finger-up event are detected within a predetermined time period, regardless of whether the contacts are above or below the respective intensity thresholds during the predetermined time period, and a swipe gesture is detected based on a determination that a movement of the contact is greater than a predetermined magnitude, even if the contact exceeds the respective intensity threshold at the end of the movement of the contact. Even in implementations in which gesture detection is affected by the intensity of the contact performing the gesture (e.g., the device detects long presses more quickly when the intensity of the contact exceeds an intensity threshold, or the device is slow to detect tap inputs when the intensity of the contact is higher), detection of those gestures does not require the contact to reach a particular intensity threshold, as long as the criteria for recognizing the gesture can be met in situations in which the contact does not reach the particular intensity threshold (e.g., even if the amount of time required to recognize the gesture varies).

[0094] The contact intensity threshold, duration threshold, and movement threshold may, in some circumstances, be combined in various different combinations to create heuristics for distinguishing between two or more different gestures directed at the same input element or region, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require that the intensity of a contact(s) meet a corresponding intensity threshold for that particular gesture recognition criterion to be satisfied does not preclude the simultaneous evaluation of other intensity-dependent gesture recognition criteria to identify other gestures with criteria that are satisfied when the gesture includes a contact having an intensity above the corresponding intensity threshold. For example, in some circumstances, 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 that first gesture recognition criterion to be satisfied competes with a second gesture recognition criterion for a second gesture that depends on the contact(s) reaching a corresponding intensity threshold. In such a competition, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the corresponding intensity threshold before moving a predetermined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves a predetermined amount of movement before reaching the corresponding intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet the corresponding intensity threshold for the first gesture recognition criteria to be satisfied, because if the contact remained below the corresponding intensity threshold until the end of the gesture (e.g., a swipe gesture with a contact that does not increase in intensity above the corresponding intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture.In this way, certain gesture recognition criteria that do not require the intensity of the contact(s) to meet a corresponding intensity threshold for the particular gesture recognition criterion to be satisfied are still dependent on the intensity of the contact with respect to an intensity threshold, in the sense that (A) in some circumstances, they ignore the intensity of the contact with respect to the intensity threshold (e.g., for a tap gesture), and / or (B) in some circumstances, the particular gesture recognition criterion (e.g., for a long press gesture) will not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes an 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 that competes with a deep press gesture for recognition).

[0095] Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for modifying the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, video, and animation.

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

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

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

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

[0100] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Videoconferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ●Training support module 142, a camera module 143 for still and / or video images, ● Image management module 144; ● Browser module 147, ● Calendar module 148, A widget module 149, optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, • Optionally, a video and music player module 152, comprising 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 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice duplication.

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

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

[0104] In conjunction with RF circuitry 108, audio circuitry 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, videoconferencing module 139 includes executable instructions for initiating, conducting, and terminating videoconferences between a user and one or more other participants according to the user's commands.

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

[0106] In cooperation with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, instant message module 141 includes executable instructions for entering a series of characters corresponding to an instant message, modifying previously entered characters, sending individual instant messages (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-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, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant message" 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 cooperation with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the video and music player module 152, the training support module 142 includes executable instructions to create workouts (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (in the sports device and the smartwatch), receive training sensor data, calibrate sensors used to monitor workouts, select and play music for workouts, and display, store, and transmit workout data.

[0108] Camera module 143, along with touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, includes executable instructions to capture still images or video (including video streams) and store them in memory 102, change characteristics of the still images or video, and / or delete the still images or video from memory 102.

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

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

[0111] Calendar module 148, along with RF circuitry 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, includes executable instructions to create, display, modify, and store calendars and data associated with the calendars (e.g., calendar entries, to-do lists, etc.) according to user commands.

[0112] Widget modules 149, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, are optionally mini-applications downloaded and used by a user (e.g., weather widget 149-1, stock quotes widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or mini-applications created by a user (e.g., user-created widget 149-6). In some embodiments, widgets include Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, widgets include Extensible Markup Language (XML) files and JavaScript files (e.g., Yahoo! Widgets).

[0113] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 contains executable instructions for creating widgets (e.g., turning user-specified portions of a web page into widgets).

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

[0115] In cooperation with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that enable a 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 instructions to display, present, or otherwise play video (e.g., on touch-sensitive display system 112 or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

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

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

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

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

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

[0121] The set of predefined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, home menu, or root menu from any user interface displayed on device 100. 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] 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (in FIG. 3) includes an event sorter 170 (e.g., within operating system 126) and a separate application 136-1 (e.g., any of applications 136, 137-155, 380-390 described above).

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

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

[0125] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user's touch on touch-sensitive display system 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

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

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

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

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

[0130] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which the initiating sub-event occurs (i.e., the first sub-event in a series of sub-events that form an event or potential event). Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

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

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

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

[0135] A separate event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies events from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

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

[0137] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes definitions of events (e.g., a predefined sequence of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, the sub-events in Event 187 include, for example, a touch start, a touch end, a touch movement, a touch cessation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) for a predetermined stage on the displayed object, a first lift-off (touch end) for a predetermined stage, a second touch (touch start) for a predetermined stage on the displayed object, and a second lift-off (touch end) for a predetermined stage. In another example, a definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) of a predetermined magnitude on a displayed object, a movement of the touch across the touch-sensitive display system 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information about one or more associated event handlers 190.

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

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

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

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

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

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

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

[0145] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of an individual application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

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

[0147] 1C is a block diagram illustrating a tactile output module, according to some embodiments. In some embodiments, I / O subsystem 106 (e.g., haptic feedback controller 161 (FIG. 1A) and / or other input controller(s) 160 (FIG. 1A) includes at least some of the example components shown in FIG. 1C. In some embodiments, peripherals interface 118 includes at least some of the example components shown in FIG. 1C.

[0148] In some embodiments, the tactile output module includes a haptic feedback module 133. In some embodiments, the haptic feedback module 133 aggregates and combines tactile output in response to user interface feedback from software applications on the electronic device (e.g., user input corresponding to a displayed user interface, and feedback responsive to alerts and other notifications indicating the performance of actions or the occurrence of events in the user interface of the electronic device). The haptic feedback module 133 includes one or more of a waveform module 123 (which provides the waveforms used to generate the tactile output), a mixer 125 (which mixes waveforms, such as waveforms for different channels), a compressor 127 (which reduces or compresses the dynamic range of the waveforms), a low-pass filter 129 (which filters high-frequency signal components in the waveforms), and a thermal controller 131 (which adjusts the waveform according to thermal conditions). In some embodiments, the haptic feedback controller 161 ( FIG. 1A ) includes the haptic feedback module 133. In some embodiments, a separate unit of haptic feedback module 133 (or a separate implementation of haptic feedback module 133) is also included in the audio controller (e.g., audio circuit 110 of FIG. 1A) and used to generate audio signals. In some embodiments, a single haptic feedback module 133 is used to generate waveforms for audio signals and tactile outputs.

[0149] In some embodiments, haptic feedback module 133 also includes trigger module 121 (e.g., a software application, operating system, or other software module that determines a tactile output to be generated and initiates the process of generating the corresponding tactile output). In some embodiments, trigger module 121 generates a trigger signal that initiates the generation of a waveform (e.g., by waveform module 123). For example, trigger module 121 generates the trigger signal based on pre-set timing criteria. In some embodiments, trigger module 121 receives trigger signals from outside haptic feedback module 133 (e.g., in some embodiments, haptic feedback module 133 receives trigger signals from hardware input processing module 146, which is located outside 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., an intensity-sensitive input surface such as a home button or an intensity-sensitive touchscreen), and relays those trigger signals to other components within haptic feedback module 133 (e.g., waveform module 123) or software applications that trigger actions (e.g., by trigger module 121). In some embodiments, trigger module 121 also receives tactile feedback generation instructions (e.g., from haptic feedback module 133, FIGS. 1A and 3). In some embodiments, trigger module 121 generates a trigger signal in response to haptic feedback module 133 (or trigger module 121 within haptic feedback module 133) receiving a tactile feedback instruction (e.g., from haptic feedback module 133, FIGS. 1A and 3).

[0150] The waveform module 123 receives as input a trigger signal (e.g., from the trigger module 121) 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 inputs and mixes these waveforms together. For example, when mixer 125 receives two or more waveforms (e.g., a first waveform in a first channel and a second waveform in a second channel that at least partially overlaps with the first waveform), mixer 125 outputs a combined waveform that corresponds 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 to emphasize a particular waveform relative to 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 remove from the combined waveform (e.g., when there are waveforms from four or more sources requested to be output simultaneously by tactile output generator 167, the waveform from the oldest source is dropped).

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

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

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

[0155] In some embodiments, haptic feedback module 133 (e.g., trigger module 121) is coupled to hardware input processing module 146. In some embodiments, other input controller(s) 160 of FIG. 1A includes hardware input processing module 146. In some embodiments, hardware input processing module 146 receives input from hardware input device 145 (e.g., other input or control device 116 of FIG. 1A, such as a home button or an intensity-sensitive input surface such as an intensity-sensitive touchscreen). In some embodiments, hardware input device 145 is any of touch-sensitive display system 112 (FIG. 1A), keyboard / mouse 350 (FIG. 3), touchpad 355 (FIG. 3), one of other input or control devices 116 (FIG. 1A), or an input device such as an intensity-sensitive home button. In some embodiments, hardware input device 145 consists of an intensity-sensitive home button and is not touch-sensitive display system 112 (FIG. 1A), keyboard / mouse 350 (FIG. 3), or touchpad 355 (FIG. 3). In some embodiments, in response to input from hardware input device 145 (e.g., an intensity-sensitive home button or a touchscreen), hardware input processing module 146 provides one or more trigger signals to haptic feedback module 133 to indicate that a user input that meets predetermined input criteria has been detected, such as an input corresponding to a home button "click" (e.g., a "down click" or an "up click"). In some embodiments, haptic feedback module 133, in response to an input corresponding to a home button "click," provides a waveform corresponding to a home button "click" to simulate the haptic feedback of pressing a physical home button.

[0156] In some embodiments, the tactile output module includes a haptic feedback controller 161 (haptic feedback controller 161 in FIG. 1A ) that controls generation of the tactile output. In some embodiments, the haptic feedback controller 161 is coupled to a plurality of tactile output generators, selects one or more of the plurality of tactile output generators, and sends waveforms to the selected one or more tactile output generators that generate the tactile output. In some embodiments, the haptic feedback controller 161 aggregates tactile output requests corresponding to activation of the hardware input device 145 and tactile output requests corresponding to software events (e.g., tactile output requests from the haptic feedback module 133), modifies one or more of the two or more waveforms, emphasizes a particular waveform relative to 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, such as to prioritize tactile output corresponding to activation of the hardware input device 145 over tactile output corresponding to the software event).

[0157] In some embodiments, as shown in FIG. 1C , the output of haptic feedback controller 161 is coupled to an audio circuit of device 100 (e.g., audio circuit 110, FIG. 1A ) and provides an audio signal to the audio circuit of device 100. In some embodiments, haptic feedback controller 161 provides both a waveform used to generate the tactile output and an audio signal used to provide the audio output in conjunction with generating the tactile output. In some embodiments, 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, haptic feedback controller 161 includes a digital-to-analog converter used to convert the digital waveform to an analog signal, which is received by amplifier 163 and / or tactile output generator 167.

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

[0159] In some embodiments, tactile output module includes sensor 169 coupled to tactile output generator 167. Sensor 169 detects the state or state change (e.g., mechanical position, physical displacement, and / or movement) of tactile output generator 167 or one or more components of tactile output generator 167 (e.g., one or more moving parts, such as a membrane used to generate the tactile output). In some embodiments, sensor 169 is a magnetic field sensor (e.g., a Hall Effect sensor) or other displacement and / or movement sensor. In some embodiments, sensor 169 provides information (e.g., the position, displacement, and / or movement of one or more parts within tactile output generator 167) to tactile feedback controller 161, which adjusts the waveform output from tactile feedback controller 161 (e.g., the waveform sent to tactile output generator 167, optionally via amplifier 163) according to the information provided by sensor 169 regarding the state of tactile output generator 167.

[0160] FIG. 2 illustrates portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A ) according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In these embodiments, as well as embodiments described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

[0161] Device 100 also optionally includes one or more physical buttons, such as a "home" or menu button 204. As mentioned above, menu button 204 is optionally used to navigate to any application 136 in a set of applications optionally running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within 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 powering the device on / off and locking the device, volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined time has elapsed, and / or to unlock the device or initiate the unlocking process. In some embodiments, device 100 also accepts verbal input through microphone 113 to activate or deactivate some features. Device 100 also optionally includes one or more contact intensity sensors 165 that detect the intensity of a contact on touch-sensitive display system 112 and / or one or more tactile output generators 167 that generate a tactile output for a user of device 100.

[0163] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a 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. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, which includes display 340, which is typically a touchscreen display. I / O interface 330 optionally also 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 outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A ), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU(s) 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disc authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store those modules.

[0164] 3 is optionally stored in one or more of the memory devices mentioned above. Each of the above-identified modules corresponds to an instruction set that performs the functions described above. The above-identified modules or programs (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, 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 above-identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0165] Attention is now directed to embodiments of a user interface (“UI”) that is optionally implemented on portable multifunction device 100.

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

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

[0168] 4B shows an exemplary user interface on a device (e.g., device 300, FIG. 3) having touch-sensitive surface 451 (e.g., tablet or touchpad 355, FIG. 3) separate from 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 a contact on touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating a tactile output for a user of device 300.

[0169] While many of the following examples are given with reference to input on touchscreen display 112 (when the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a major axis (e.g., 452 in FIG. 4B ) that corresponds to a major axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B ) with touch-sensitive surface 451 at positions that correspond to respective positions on the display (e.g., 460 corresponds to 468, and 462 corresponds to 470 in FIG. 4B ). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462, and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It should be understood that similar methods are optionally used for other user interfaces described herein.

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

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

[0172] As used herein and in the claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or a proxy for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four distinct values ​​and more typically includes hundreds (e.g., at least 256) distinct values. The intensity of a contact is optionally determined (or measured) using various techniques and various sensors or combinations of sensors. For example, one or more force sensors under or adjacent to the touch-sensitive surface are optionally used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average or sum) to determine an estimated force of the contact. Similarly, a pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size and / or change in the contact area detected on the touch-sensitive surface, the capacitance and / or change in the capacitance of the touch-sensitive surface proximate the contact, and / or the resistance and / or change in the capacitance of the touch-sensitive surface proximate the contact are optionally used as a surrogate for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measure 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 stated in units corresponding to the surrogate measure). In some implementations, the surrogate measure for the force or pressure of the contact is converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold is exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).Using the intensity of contact as an attribute of user input allows a user to access additional functionality that, in some circumstances, is not otherwise easily accessible by a user on a reduced-size device having 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 controls such as knobs or buttons).

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

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

[0175] In some embodiments, a portion of the gesture is identified for purposes of determining the characteristic intensity. For example, the touch-sensitive surface optionally receives successive swipe contacts (e.g., a drag gesture) that transition from a start position to an end position where the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end position may, in some circumstances, be based on only a portion of the successive swipe contacts (e.g., only the portion of the swipe contact at the end position) rather than the entire successive swipe contacts. In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, ...

Claims

1. 1. A method comprising:

1. A computer system in communication with a display generation component, comprising: Displaying a first user interface, the first user interface includes a first plurality of user interface objects corresponding to different applications displayed at respective positions within the first user interface; the first user interface includes locations configured to spatially accommodate individual user interface objects of a second plurality of user interface objects corresponding to different applications; the second plurality of user interface objects includes 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; the first user interface object corresponding to the first application is displayed at the location; And, Detecting the occurrence of an event associated with a change in state of the second application corresponding to the second user interface object; In response to detecting the occurrence of the event associated with the change in state of the second application, ceasing to display the first user interface object corresponding to the first application at the location and displaying the first user interface with the second user interface object corresponding to the second application displayed at the location within the first user interface while maintaining the display of the first plurality of user interface objects at their respective locations within the first user interface; After displaying the second user interface object at the placement location, automatically updating content displayed at the placement location while maintaining the display of the first plurality of user interface objects at the respective locations within the first user interface, removing the second user interface object corresponding to the second application from the display in the first user interface; redisplaying the first user interface with the first user interface object corresponding to the first application displayed at the location while maintaining the display of the first plurality of user interface objects at the respective locations within the first user interface; and A method comprising:

2. 10. The method of claim 1 further comprising: detecting a context change in the computer system while displaying a third user interface object of the second plurality of user interface objects at the location within the first user interface, the third user interface object corresponding to a third application; In response to detecting the context change in the computer system, ceasing to display the third user interface object corresponding to the third application at the location; and displaying the first user interface together with a fourth user interface object of the second plurality of user interface objects at the location, the fourth user interface object corresponding to a fourth application different from the third application; A method comprising:

3. 3. The method of claim 2, Detecting a context change in the computer system includes detecting a change in a current location of the computer system; the fourth user interface object is selected for display at the location based on the current location of the computer system. method.

4. 3. The method of claim 2, wherein the fourth user interface object is selected for display at the location based on a current time. method.

5. 10. The method of claim 1 further comprising: in response to determining that a predetermined time has elapsed while a third user interface object corresponding to a third application among the second plurality of user interface objects is displayed at the placement position within the first user interface, ceasing to display the third user interface object corresponding to the third application at the location; and displaying the first user interface together with a fifth user interface object of the second plurality of user interface objects at the location, the fifth user interface object corresponding to a fifth application different from the third application; A method comprising:

6. 10. The method of claim 1 further comprising: detecting a context change indicating that the computer system has been placed in proximity to a second computer system different from the first computer system while displaying a third user interface object of the second plurality of user interface objects corresponding to a third application at the placement location within the first user interface; In response to detecting the context change indicating that the computer system has been placed in proximity to the second computer system, ceasing to display the third user interface object corresponding to the third application at the location; and displaying the first user interface together with a sixth user interface object of the second plurality of user interface objects at the location, the sixth user interface object corresponding to a digital wallet application; A method comprising:

7. 10. The method of claim 1 further comprising: receiving an incoming communication at the computer system while displaying a third user interface object of the second plurality of user interface objects at the location within the first user interface, the third user interface object corresponding to a third application; in response to receiving the incoming communication at the computer system, ceasing to display the third user interface object corresponding to the third application at the location; and displaying the first user interface together with a seventh user interface object of the second plurality of user interface objects at the location, the seventh user interface object corresponding to a communications application; and A method comprising:

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

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

10. 10. The method of claim 1 further comprising: detecting an input directed at the second user interface object while displaying the first user interface with the second user interface object displayed at the location; In response to detecting the input directed to the second user interface object, redisplaying the first user interface with the first user interface object corresponding to the first application at the location; A method comprising:

11. 10. The method of claim 1, detecting an input directed at an individual user interface object of the second plurality of user interface objects displayed at the placement location while the individual user interface object is displayed at the placement location; In response to detecting the input directed to the individual user interface object displayed at the placement location, displaying a user interface of an application corresponding to the individual user interface object; A method comprising:

12. 12. The method of claim 11, further comprising ceasing to display the individual user interface object at the location in response to detecting the input directed at the individual user interface object displayed at the location. A method comprising:

13. 10. The method of claim 1, wherein the first user interface includes a plurality of locations, and wherein an individual user interface object currently displayed in a first location of the plurality of locations is updated independently from an individual user interface object currently displayed in a second location of the plurality of locations. method.

14. 14. The method of claim 13, wherein the individual user interface objects currently displayed in the first location include content of a first individual application, and the individual user interface objects currently displayed in the second location include content of a second individual application that is different from the first individual application. method.

15. 1. A computer system comprising: a display generation component; one or more processors; a memory storing one or more programs, the one or more programs being configured to be executed by the one or more processors, the one or more programs being Displaying a first user interface, the first user interface includes a first plurality of user interface objects corresponding to different applications displayed at respective positions within the first user interface; the first user interface includes locations configured to spatially accommodate individual user interface objects of a second plurality of user interface objects corresponding to different applications; the second plurality of user interface objects includes 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; the first user interface object corresponding to the first application is displayed at the location; And, Detecting the occurrence of an event associated with a change in state of the second application corresponding to the second user interface object; In response to detecting the occurrence of the event associated with the change in state of the second application, ceasing to display the first user interface object corresponding to the first application at the location and displaying the first user interface with the second user interface object corresponding to the second application displayed at the location within the first user interface while maintaining the display of the first plurality of user interface objects at their respective locations within the first user interface; After displaying the second user interface object at the placement location, automatically updating content displayed at the placement location while maintaining the display of the first plurality of user interface objects at the respective locations within the first user interface, removing the second user interface object corresponding to the second application from the display in the first user interface; redisplaying the first user interface with the first user interface object corresponding to the first application displayed at the location while maintaining the display of the first plurality of user interface objects at the respective locations within the first user interface; and a computer system including instructions for performing the steps of:

16. 16. A computer system according to claim 15, wherein the one or more programs comprise instructions for carrying out the method of any one of claims 2 to 14. Computer system.

17. 1. A program comprising instructions that, when executed by a computer system having a display and an input element, cause the computer system to: Displaying a first user interface, the first user interface includes a first plurality of user interface objects corresponding to different applications displayed at respective positions within the first user interface; the first user interface includes locations configured to spatially accommodate individual user interface objects of a second plurality of user interface objects corresponding to different applications; the second plurality of user interface objects includes 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; the first user interface object corresponding to the first application is displayed at the location; And, Detecting the occurrence of an event associated with a change in state of the second application corresponding to the second user interface object; In response to detecting the occurrence of the event associated with the change in state of the second application, ceasing to display the first user interface object corresponding to the first application at the location and displaying the first user interface with the second user interface object corresponding to the second application displayed at the location within the first user interface while maintaining the display of the first plurality of user interface objects at their respective locations within the first user interface; After displaying the second user interface object at the placement location, automatically updating content displayed at the placement location while maintaining the display of the first plurality of user interface objects at the respective locations within the first user interface, removing the second user interface object corresponding to the second application from the display in the first user interface; redisplaying the first user interface with the first user interface object corresponding to the first application displayed at the location while maintaining the display of the first plurality of user interface objects at the respective locations within the first user interface; and A program that performs the following.

18. 18. The program of claim 17, further comprising instructions which, when executed by the computer system, cause the computer system to perform the method of any one of claims 2 to 14. program.

Images