Device, method, and graphical user interface for manipulating user interface objects

Description

TECHNICAL FIELD

The disclosed embodiments relate generally to electronic devices with touch-sensitive surfaces, and more particularly, to electronic devices with touch-sensitive surfaces that use two or more simultaneous user inputs to manipulate user interface objects.

BACKGROUND

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 touch pads and touch screen displays. Such surfaces are widely used to manipulate user interface objects on a display.

Exemplary manipulations include adjusting the position and/or size of one or more user interface objects, as well as associating metadata with one or more user interface objects. Exemplary user interface objects include digital images, video, text, icons, and other graphics. A user may need to perform such manipulations on user interface objects in a file management program (e.g., Finder from Apple Computer, Inc. of Cupertino, California), an image management application (e.g., Aperture or iPhoto from Apple Computer, Inc. of Cupertino, California), a digital content (e.g., videos and music) management application (e.g., iTunes from Apple Computer, Inc. of Cupertino, California), a drawing application, a presentation application (e.g., Keynote from Apple Computer, Inc. of Cupertino, California), a word processing application (e.g., Pages from Apple Computer, Inc. of Cupertino, California), a website creation application (e.g., iWeb from Apple Computer, Inc. of Cupertino, California), a disk authoring application (e.g., iDVD from Apple Computer, Inc. of Cupertino, California), or a spreadsheet application (e.g., Numbers from Apple Computer, Inc. of Cupertino, California).

But existing methods for performing these manipulations are cumbersome and inefficient. For example, using a sequence of mouse-based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and creates a significant cognitive burden on a user. Existing methods that use simultaneous inputs to perform these manipulations are also cumbersome and inefficient. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.

Accordingly, there is a need for computing devices with faster, more efficient methods and interfaces for manipulating user interface objects using two or more simultaneous user inputs, such as two simultaneous inputs on a track pad or touch screen, or simultaneous inputs from a touch-sensitive surface and a mouse. Such methods and interfaces may complement or replace conventional methods for manipulating user interface objects. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

SUMMARY

The above deficiencies and other problems associated with user interfaces for computing devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions may include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions may be included in a computer readable storage medium or other computer program product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes: simultaneously displaying on the touch screen display: a plurality of user interface objects, and at least one destination object; and detecting a first input by a user on a destination object. The method further includes, while continuing to detect the first input by the user on the destination object: detecting a second input by the user on a first user interface object displayed at an initial first user interface object position on the touch screen display; and, in response to detecting the second input by the user on the first user interface object, performing an action on the first user interface object. The action is associated with the destination object.

In accordance with some embodiments, a computing device includes: a touch screen display; means for simultaneously displaying on the touch screen display: a plurality of user interface objects, and at least one destination object. The device also includes means for detecting a first input by a user on a destination object. The device further includes, while continuing to detect the first input by the user on the destination object, means for detecting a second input by the user on a first user interface object displayed at an initial first user interface object position on the touch screen display; and, means, responsive to detecting the second input by the user on the first user interface object, for performing an action on the first user interface object. The action is associated with the destination object.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes: simultaneously displaying on the touch screen display a plurality of user interface objects, and at least one destination object; and detecting a first input by a user on a destination object. The method further includes, while continuing to detect the first input by the user on the destination object: detecting a second input by the user or a series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and, in response to detecting the second input by the user or series of inputs by the user on the two or more user interface objects, performing an action on each of the two or more user interface objects. The action is associated with the destination object.

In accordance with some embodiments, a computing device includes: a touch screen display; means for simultaneously displaying on the touch screen display: a plurality of user interface objects, and at least one destination object. The device further includes means for detecting a first input by a user on a destination object. The device also includes, while continuing to detect the first input by the user on the destination object: means for detecting a second input by the user or a series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and means, responsive to detecting the second input by the user or series of inputs by the user on the two or more user interface objects, for performing an action on each of the two or more user interface objects. The action is associated with the destination object.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes: simultaneously displaying on the touch screen display a plurality of user interface objects and at least one destination object. The method also includes detecting a first input by a user on a first user interface object at a first location on the touch screen display. The method further includes, while continuing to detect the first input by the user: detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display; moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; detecting a second input by the user on a second user interface object displayed at an initial second user interface object position on the touch screen display; and, in response to detecting the second input by the user on the second user interface object, displaying an animation of the second user interface object moving from the initial second user interface object position to the second location.

In accordance with some embodiments, a computing device includes: a touch screen display; and means for simultaneously displaying on the touch screen display: a plurality of user interface objects, and at least one destination object. The device also includes means for detecting a first input by a user on a first user interface object at a first location on the touch screen display. The device further includes, while continuing to detect the first input by the user: means for detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display; means for moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; means for detecting a second input by the user on a second user interface object displayed at an initial second user interface object position on the touch screen display; and, means, responsive to detecting the second input by the user on the second user interface object, for displaying an animation of the second user interface object moving from the initial second user interface object position to the second location.

In accordance with some embodiments, an information processing apparatus for use in a computing device with a touch screen display includes: means for simultaneously displaying on the touch screen display a plurality of user interface objects and at least one destination object; and means for detecting a first input by a user on a first user interface object at a first location on the touch screen display. The apparatus further includes, while continuing to detect the first input by the user: means for detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display; means for moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; means for detecting a second input by the user on a second user interface object displayed at an initial second user interface object position on the touch screen display; and, means, responsive to detecting the second input by the user on the second user interface object, for displaying an animation of the second user interface object moving from the initial second user interface object position to the second location.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes: simultaneously displaying on the touch screen display a plurality of user interface objects and at least one destination object. The method also includes detecting a first input by a user on a first user interface object at a first location on the touch screen display. The method further includes, while continuing to detect the first input by the user: detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display; moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; detecting a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and, in response to detecting the second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, displaying animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to the second location.

In accordance with some embodiments, a computing device includes a touch screen display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for simultaneously displaying on the touch screen display a plurality of user interface objects and at least one destination object. The programs also include instructions for detecting a first input by a user on a first user interface object at a first location on the touch screen display. The programs further include instructions for, while continuing to detect the first input by the user: detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display; moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; detecting a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and, in response to detecting the second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, displaying animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to the second location.

In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by a computing device with a touch screen display, cause the device to simultaneously display on the touch screen display a plurality of user interface objects and at least one destination object. The instructions also cause the device to detect a first input by a user on a first user interface object at a first location on the touch screen display. The instructions further cause the device to, while continuing to detect the first input by the user; detect movement of the first input by the user across the touch screen display to a second location on the touch screen display; move the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; detect a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and, in response to detecting the second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, display animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to the second location.

In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display, a memory, and one or more processors to execute one or more programs stored in the memory includes a plurality of user interface objects and at least one destination object. A first input by a user is detected on a first user interface object at a first location on the touch screen display. While continuing to detect the first input by the user: movement of the first input by the user across the touch screen display to a second location on the touch screen display is detected; the first user interface object is moved in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects is detected, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and, in response to detecting the second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to the second location are displayed.

In accordance with some embodiments, a computing device includes: a touch screen display; and means for simultaneously displaying on the touch screen display a plurality of user interface objects and at least one destination object. The device also includes means for detecting a first input by a user on a first user interface object at a first location on the touch screen display. The device further includes, while continuing to detect the first input by the user: means for detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display; means for moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; means for detecting a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and means, responsive to detecting the second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, for displaying animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to the second location.

In accordance with some embodiments, an information processing apparatus for use in a computing device with a touch screen display includes: means for simultaneously displaying on the touch screen display a plurality of user interface objects and at least one destination object. The apparatus also includes means for detecting a first input by a user on a first user interface object at a first location on the touch screen display. The apparatus further includes, while continuing to detect the first input by the user: means for detecting movement of the first input by the user across the touch screen display to a second location on the touch screen display: means for moving the first user interface object in accordance with the movement of the first input by the user across the touch screen display to the second location on the touch screen display; means for detecting a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, wherein the two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display; and means, responsive to detecting the second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects, for displaying animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to the second location.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes simultaneously displaying on the touch screen display a plurality of user interface objects in an array. The plurality of user interface objects in the array is displayed in a first arrangement. A first user interface object in the plurality of user interface objects is displayed at a first size. The first arrangement comprises a first plurality of rows. The method further includes detecting simultaneous contacts by a plurality of fingers on the array. The simultaneous contacts have a corresponding centroid position at the first user interface object. The method also includes detecting a gesture made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount; and, in response to detecting the gesture by the simultaneous contacts, enlarging the first user interface object to a second size larger than the first size on the touch screen display. The method further includes, after enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, determining an updated centroid position of the simultaneous contacts. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. The method also includes ceasing to detect the simultaneous contacts; and, in response to ceasing to detect the simultaneous contacts, displaying an animation of the plurality of user interface objects in the array rearranging to form a second arrangement. The second arrangement comprises a second plurality of rows different from the first plurality of rows. The first user interface object is displayed in a row in the second arrangement that includes the first vertical position on the touch screen display.

In accordance with some embodiments, a computing device includes a touch screen display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for simultaneously displaying on the touch screen display a plurality of user interface objects in an array. The plurality of user interface objects in the array is displayed in a first arrangement. A first user interface object in the plurality of user interface objects is displayed at a first size. The first arrangement comprises a first plurality of rows. The programs also include instructions for detecting simultaneous contacts by a plurality of fingers on the array. The simultaneous contacts have a corresponding centroid position at the first user interface object. The programs further include instructions for: detecting a gesture made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount; in response to detecting the gesture by the simultaneous contacts, enlarging the first user interface object to a second size larger than the first size on the touch screen display: and, after enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, determining an updated centroid position of the simultaneous contacts. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. The program also includes instructions for: ceasing to detect the simultaneous contacts; and, in response to ceasing to detect the simultaneous contacts, displaying an animation of the plurality of user interface objects in the array rearranging to form a second arrangement. The second arrangement comprises a second plurality of rows different from the first plurality of rows, and the first user interface object is displayed in a row in the second arrangement that includes the first vertical position on the touch screen display.

In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by a computing device with a touch screen display, cause the device to simultaneously display on the touch screen display a plurality of user interface objects in an array. The plurality of user interface objects in the array is displayed in a first arrangement. A first user interface object in the plurality of user interface objects is displayed at a first size. The first arrangement comprises a first plurality of rows. The instructions also cause the device to detect simultaneous contacts by a plurality of fingers on the array. The simultaneous contacts have a corresponding centroid position at the first user interface object. The instructions further cause the device to: detect a gesture made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount; in response to detecting the gesture by the simultaneous contacts, enlarge the first user interface object to a second size larger than the first size on the touch screen display; and, after enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, determine an updated centroid position of the simultaneous contacts. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. The instructions also cause the device to: cease to detect the simultaneous contacts; and, in response to ceasing to detect the simultaneous contacts, display an animation of the plurality of user interface objects in the array rearranging to form a second arrangement. The second arrangement comprises a second plurality of rows different from the first plurality of rows. The first user interface object is displayed in a row in the second arrangement that includes the first vertical position on the touch screen display.

In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display, a memory, and one or more processors to execute one or more programs stored in the memory includes a plurality of user interface objects in an array. The plurality of user interface objects in the array is displayed in a first arrangement. A first user interface object in the plurality of user interface objects is displayed at a first size. The first arrangement comprises a first plurality of rows. Simultaneous contacts by a plurality of fingers are detected on the array. The simultaneous contacts have a corresponding centroid position at the first user interface object. A gesture made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount is detected. In response to detecting the gesture by the simultaneous contacts, the first user interface object is enlarged to a second size larger than the first size on the touch screen display. After enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, an updated centroid position of the simultaneous contacts is determined. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. The simultaneous contacts cease to be detected. In response to ceasing to detect the simultaneous contacts, an animation of the plurality of user interface objects in the array rearranging to form a second arrangement is displayed. The second arrangement comprises a second plurality of rows different from the first plurality of rows. The first user interface object is displayed in a row in the second arrangement that includes the first vertical position on the touch screen display.

In accordance with some embodiments, a computing device includes: a touch screen display; and means for simultaneously displaying on the touch screen display a plurality of user interface objects in an array. The plurality of user interface objects in the array is displayed in a first arrangement. A first user interface object in the plurality of user interface objects is displayed at a first size. The first arrangement comprises a first plurality of rows. The device also includes means for detecting simultaneous contacts by a plurality of fingers on the array. The simultaneous contacts have a corresponding centroid position at the first user interface object. The device further includes: means for detecting a gesture made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount; means, responsive to detecting the gesture by the simultaneous contacts, for enlarging the first user interface object to a second size larger than the first size on the touch screen display; and means for, after enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, determining an updated centroid position of the simultaneous contacts. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. The device also includes: means for ceasing to detect the simultaneous contacts; and, means, responsive to ceasing to detect the simultaneous contacts, for displaying an animation of the plurality of user interface objects in the array rearranging to form a second arrangement. The second arrangement comprises a second plurality of rows different from the first plurality of rows. The first user interface object is displayed in a row in the second arrangement that includes the first vertical position on the touch screen display.

In accordance with some embodiments, an information processing apparatus for use in a computing device with a touch screen display includes means for simultaneously displaying on the touch screen display a plurality of user interface objects in an array. The plurality of user interface objects in the array is displayed in a first arrangement. A first user interface object in the plurality of user interface objects is displayed at a first size. The first arrangement comprises a first plurality of rows. The apparatus also includes means for detecting simultaneous contacts by a plurality of fingers on the array. The simultaneous contacts have a corresponding centroid position at the first user interface object. The apparatus further includes: means for detecting a gesture made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount; means, responsive to detecting the gesture by the simultaneous contacts, for enlarging the first user interface object to a second size larger than the first size on the touch screen display; and means for, after enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, determining an updated centroid position of the simultaneous contacts. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. The apparatus also includes: means for ceasing to detect the simultaneous contacts; and, means, responsive to ceasing to detect the simultaneous contacts, for displaying an animation of the plurality of user interface objects in the array rearranging to form a second arrangement. The second arrangement comprises a second plurality of rows different from the first plurality of rows. The first user interface object is displayed in a row in the second arrangement that includes the first vertical position on the touch screen display.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The method further includes detecting a first input by a user on the touch screen display: and, in response to detecting the first input by the user on the touch screen display, vertically scrolling the plurality of arrays on the touch screen display. The method further includes detecting a second input by the user on a single array in the plurality of arrays on the touch screen display; and, in response to detecting the second input by the user on the single array, horizontally scrolling user interface objects in the single army.

In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display, a memory, and one or more processors to execute one or more programs stored in the memory includes at least one destination object and at least a subset of a plurality of arrays of user interface objects. A first input by a user on the touch screen display is detected. In response to detecting the first input by the user on the touch screen display, the plurality of arrays on the touch screen display is vertically scrolled. A second input by the user on a single array in the plurality of arrays on the touch screen display is detected. In response to detecting the second input by the user on the single array, user interface objects in the single array are horizontally scrolled.

In accordance with some embodiments, an information processing apparatus for use in a computing device with a touch screen display includes means for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The apparatus also includes: means for detecting a first input by a user on the touch screen display; and, means, responsive to detecting the first input by the user on the touch screen display, for vertically scrolling the plurality of arrays on the touch screen display. The apparatus further includes: means for detecting a second input by the user on a single array in the plurality of arrays on the touch screen display; and, means, responsive to detecting the second input by the user on the single array, for horizontally scrolling user interface objects in the single array.

In accordance with some embodiments, a method is performed at a computing device with a touch screen display. The method includes: simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The method further includes: detecting activation of a respective array name icon that corresponds to a respective array in the plurality of arrays, and, in response to detecting activation of the respective array name icon that corresponds to the respective array, displaying an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array. The method also includes: detecting movement of an input by the user from the array name icon to a destination object or an area associated with a destination object; and, moving the respective representative user interface object in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object. The method further includes: detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with a destination object; and, in response to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, performing an action on the user interface objects in the respective array. The action is associated with the destination object.

In accordance with some embodiments, a computing device includes a touch screen display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The programs also include instructions for: detecting activation of a respective array name icon that corresponds to a respective array in the plurality of arrays; and, in response to detecting activation of the respective array name icon that corresponds to the respective array, displaying an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array. The programs further include instructions for: detecting movement of an input by the user from the array name icon to a destination object or an area associated with a destination object; and moving the respective representative user interface object in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object. The programs also include instructions for: detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with a destination object; and, in response to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, performing an action on the user interface objects in the respective array. The action is associated with the destination object.

In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by a computing device with a touch screen display, cause the device to simultaneously display on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The instructions also cause the device to: detect activation of a respective array name icon that corresponds to a respective array in the plurality of arrays; and, in response to detecting activation of the respective array name icon that corresponds to the respective array, display an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array. The instructions also cause the device to: detect movement of an input by the user from the array name icon to a destination object or an area associated with a destination object; and, move the respective representative user interface object in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object. The instructions further cause the device to: detect lift off of the input by the user from the touch screen display at the destination object or at the area associated with a destination object; and, in response to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, perform an action on the user interface objects in the respective array. The action is associated with the destination object.

In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display, a memory, and one or more processors to execute one or more programs stored in the memory includes at least one destination object and at least a subset of a plurality of arrays of user interface objects. Activation of a respective array name icon that corresponds to a respective array in the plurality of arrays is detected. In response to detecting activation of the respective array name icon that corresponds to the respective array, an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array is displayed. Movement of an input by the user from the array name icon to a destination object or an area associated with a destination object is detected. The respective representative user interface object is moved in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object. Lift off of the input by the user from the touch screen display at the destination object or at the area associated with a destination object is detected. In response to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, an action on the user interface objects in the respective array is performed. The action is associated with the destination object.

In accordance with some embodiments, a computing device includes: a touch screen display; and means for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The device also includes: means for detecting activation of a respective array name icon that corresponds to a respective array in the plurality of arrays; and means, responsive to detecting activation of the respective array name icon that corresponds to the respective array, for displaying an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array. The device further includes: means for detecting movement of an input by the user from the array name icon to a destination object or an area associated with a destination object; and means for moving the respective representative user interface object in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object. The device also includes: means for detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with a destination object; and, means, responsive to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, for performing an action on the user interface objects in the respective array. The action is associated with the destination object.

In accordance with some embodiments, an information processing apparatus for use in a computing device with a touch screen display includes means for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects. The apparatus also includes: means for detecting activation of a respective array name icon that corresponds to a respective array in the plurality of arrays; and means, responsive to detecting activation of the respective array name icon that corresponds to the respective array, for displaying an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array. The apparatus further includes: means for detecting movement of an input by the user from the array name icon to a destination object or an area associated with a destination object; and means for moving the respective representative user interface object in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object. The apparatus also includes: means for detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with a destination object; and, means, responsive to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, for performing an action on the user interface objects in the respective array. The action is associated with the destination object.

In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display, a memory, and one or more processors to execute one or more programs stored in the memory includes at least one destination object and at least a subset of a plurality of arrays of user interface objects. Activation of a menu category icon is detected. In response to detecting activation of the menu category icon, a plurality of representative user interface objects for respective arrays are displayed in a menu category that corresponds to the menu category icon.

In accordance with some embodiments, a computing device includes: a touch screen display; means for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects: means for detecting activation of a menu category icon; and, means, responsive to detecting activation of the menu category icon, for displaying a plurality of representative user interface objects for respective arrays in a menu category that corresponds to the menu category icon.

In accordance with some embodiments, an information processing apparatus for use in a computing device with a touch screen display includes: means for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects; means for detecting activation of a menu category icon; and, means, responsive to detecting activation of the menu category icon, for displaying a plurality of representative user interface objects for respective arrays in a menu category that corresponds to the menu category icon.

In accordance with some embodiments, a graphical user interface on a computing device with a touch screen display, a memory, and one or more processors to execute one or more programs stored in the memory includes at least one destination object and at least a subset of a plurality of arrays of user interface objects. A first input by a user on a destination object is detected. While continuing to detect the first input by the user on the destination object, a second input by the user on an array name icon is detected. In response to detecting the second input by the user on the array name icon, an action is performed on all user interface objects in an array that corresponds to the array name icon. The action is associated with the destination object.

In accordance with some embodiments, a computing device includes: a touch screen display; means for simultaneously displaying on the touch screen display at least one destination object and at least a subset of a plurality of arrays of user interface objects; means for detecting a first input by a user on a destination object; while continuing to detect the first input by the user on the destination object, means for detecting a second input by the user on an array name icon; and, means, responsive to detecting the second input by the user on the array name icon, for performing an action on all user interface objects in an array that corresponds to the array name icon. The action is associated with the destination object.

Thus, computing devices with touch screen displays are provided with faster, more efficient methods and interfaces for manipulating user interface objects using two or more simultaneous user inputs, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for manipulating user interface objects.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of the invention as well as additional embodiments thereof, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices with touch-sensitive displays in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary computing device with a display and a touch-sensitive surface in accordance with some embodiments.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu of applications on a portable multifunction device in accordance with some embodiments.

FIG. 4C illustrates exemplary user interfaces for a device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIGS. 7A-7O illustrate exemplary user interfaces for zooming and rearranging user interface objects in an array with a multifinger gesture in accordance with some embodiments.

FIGS. 8A-8UU illustrate exemplary user interfaces for manipulating user interface objects in a plurality of arrays of user interface objects in accordance with some embodiments.

FIGS. 9A-9D are flow diagrams illustrating a method of moving one or more user interface objects to a destination object and performing an action associated with the destination object on the one or more user interface objects in accordance with some embodiments.

FIGS. 10A-10B are flow diagrams illustrating a method of moving multiple user interface objects to a destination object and performing an action associated with the destination object on the multiple user interface objects in accordance with some embodiments.

FIGS. 11A-11B are flow diagrams illustrating a method of forming a group of user interface objects, moving the group to a destination object or an area associated with a destination object, and performing an action associated with the destination object on the group of user interface objects in accordance with some embodiments.

FIGS. 12A-12B are flow diagrams illustrating a method of forming a group of user interface objects, moving the group to a destination object or an area associated with a destination object, and performing an action associated with the destination object on the group of user interface objects in accordance with some embodiments.

FIGS. 13A-13B are flow diagrams illustrating a method of zooming and rearranging user interface objects in an array with a multifinger gesture in accordance with some embodiments.

FIGS. 14A-14I are flow diagrams illustrating a method of manipulating user interface objects in a plurality of arrays of user interface objects in accordance with some embodiments.

FIGS. 15A-15B are flow diagrams illustrating a method of performing an action on user interface objects in an array in accordance with some embodiments.

FIGS. 16A-16B are flow diagrams illustrating a method of using representative user interface objects for respective arrays in a menu category to select an array in accordance with some embodiments.

FIGS. 17A-17B are flow diagrams illustrating a method of performing an action on user interface objects in an array in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to 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 present invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the present invention. The first contact and the second contact are both contacts, but they are not the same contact.

The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

Embodiments of computing devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the computing device is a portable communications device such as a mobile telephone that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone® and iPod Touch® devices from Apple, Inc. of Cupertino, California.

In the discussion that follows, a computing device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the computing device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.

The device supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications that may be executed on the device may use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device may be adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device may support the variety of applications with user interfaces that are intuitive and transparent.

The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. No. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference in their entirety. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.

Attention is now directed towards embodiments of portable devices with touch-sensitive displays. FIGS. 1A and 1B are block diagrams illustrating portable multifunction devices 100 with touch-sensitive displays 112 in accordance with some embodiments. The touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and may also be known as or called a touch-sensitive display system. The device 100 may include a memory 102 (which may include one or more computer readable storage mediums), a memory controller 122, one or more processing units (CPU's) 120, a peripherals interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input/output (I/O) subsystem 106, other input or control devices 116, and an external port 124. The device 100 may include one or more optical sensors 164. These components may communicate over one or more communication buses or signal lines 103.

It should be appreciated that the device 100 is only one example of a portable multifunction device 100, and that the device 100 may have more or fewer components than shown, may combine two or more components, or a may have a different configuration or arrangement of the components. The various components shown in FIGS. 1A and 1B may be implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.

Memory 102 may include high-speed random access memory and may also include 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 the device 100, such as the CPU 120 and the peripherals interface 118, may be controlled by the memory controller 122.

The peripherals interface 118 couples the input and output peripherals of the device to the CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for the device 100 and to process data.

In some embodiments, the peripherals interface 118, the CPU 120, and the memory controller 122 may be implemented on a single chip, such as a chip 104. In some other embodiments, they may be implemented on separate chips.

The RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. The RF circuitry 108 may include well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. The RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (IAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence 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.

The audio circuitry 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuitry 110 receives audio data from the peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal to human-audible sound waves. The audio circuitry 110 also receives electrical signals converted by the microphone 113 from sound waves. The audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to the peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or the RF circuitry 108 by the peripherals interface 118. In some embodiments, the audio circuitry 110 also includes a headset jack (e.g. 212, FIG. 2). The headset jack provides an interface between the audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input/control devices 116, to the peripherals interface 118. The I/O subsystem 106 may include a display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input/control devices 116 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) may include an up/down button for volume control of the speaker 111 and/or the microphone 113. The one or more buttons may include a push button (e.g., 206, FIG. 2). A quick press of the push button may disengage a lock of the touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to the device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

The touch-sensitive touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and/or sends electrical signals from/to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.

A touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. The touch screen 112 and the display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on the touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen 112 and the user corresponds to a finger of the user.

The touch screen 112 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. The touch screen 112 and the display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with a touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple, Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of the touch screen 112 may be analogous to the multi-touch sensitive tablets described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, a touch screen 112 displays visual output from the portable device 100, whereas touch sensitive tablets do not provide visual output.

A touch-sensitive display in some embodiments of the touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller.” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscrcen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590. “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700. “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

The touch screen 112 may have a resolution in excess of 100 dpi. In an exemplary embodiment, the touch screen has a resolution of approximately 160 dpi. The user may make contact with the touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which am much less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, the device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

In some embodiments, the device 100 may include a physical or virtual click wheel as an input control device 116. A user may navigate among and interact with one or more graphical objects (e.g., icons) displayed in the touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by an input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of the touch screen 112 and the display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.

The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

The device 100 may also include one or more optical sensors 164. FIGS. 1A and 1B show an optical sensor coupled to an optical sensor controller 158 in I/O subsystem 106. The optical sensor 164 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. The optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with an imaging module 143 (also called a camera module), the optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of the device 100, opposite the touch screen display 112 on the front of the device, so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user's image may be obtained for videoconferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition.

The device 100 may also include one or more proximity sensors 166. FIGS. 1A and 1B show a proximity sensor 166 coupled to the peripherals interface 118. Alternately, the proximity sensor 166 may be coupled to an input controller 160 in the I/O subsystem 106. The proximity sensor 166 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector in Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

The device 100 may also include one or more accelerometers 168. FIGS. 1A and 1B show an accelerometer 168 coupled to the peripherals interface 118. Alternately, the accelerometer 168 may be coupled to an input controller 160 in the I/O subsystem 106. The accelerometer 168 may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers.

In some embodiments, the software components stored in memory 102 may include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and applications (or set of instructions) 136.

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

The communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by the RF circuitry 108 and/or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple, Inc.) devices.

The contact/motion module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, may include determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detects contact on a touchpad. In some embodiments, the contact/motion module 130 and the controller 160 detects contact on a click wheel.

The contact/motion module 130 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up event.

The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the intensity of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic may be assigned a corresponding code. The graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

The text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

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

The applications 136 may include 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);
- a telephone module 138;
- a video conferencing module 139;
- an e-mail client module 140;
- an instant messaging (1M) module 141;
- a workout support module 142;
- a camera module 143 for still and/or video images;
- an image management module 144;
- a video player module 145;
- a music player module 146;
- a browser module 147;
- a calendar module 148;
- widget modules 149, which may include weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
- widget creator module 150 for making user-created widgets 149-6;
- search module 151;
- video and music player module 152, which merges video player module 145 and music player module 146;
- notes module 153;
- map module 154; and/or
- online video module 155.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the contacts module 137 may be used to manage an address book or contact list, including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, the videoconferencing module 139 may be used to initiate, conduct, and terminate a video conference between a user and one or more other participants.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the e-mail client module 140 may be used to create, send, receive, and manage e-mail. In conjunction with image management module 144, the e-mail module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 may be used to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, the workout support module 142 may be used to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices): receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, the camera module 143 may be used to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, the image management module 144 may be used to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, the video player module 145 may be used to display, present or otherwise play back videos (e.g., on the touch screen or on an external, connected display via external port 124).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, the music player module 146 allows the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files. In some embodiments, the device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple. Inc.).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the browser module 147 may be used to browse the Internet, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail module 140, and browser module 147, the calendar module 148 may be used to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, the search module 151 may be used to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 may be used to create and manage notes, to do lists, and the like.

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

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, the online video module 155 allows the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the content of which is hereby incorporated by reference in its entirety.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152, FIG. 1B). In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.

In some embodiments, the device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen 112 and/or a touchpad. By using a touch screen and/or a touchpad as the primary input/control device for operation of the device 100, the number of physical input/control devices (such as push buttons, dials, and the like) on the device 100 may be reduced.

The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main, home, or root menu from any user interface that may be displayed on the device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input/control device instead of a touchpad.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen may display one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user may select one or more of the graphics by making contact or touching the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the contact may include a gesture, such as one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with the device 100. In some embodiments, inadvertent contact with a graphic may not select the graphic. For example, a swipe gesture that sweeps over an application icon may not select the corresponding application when the gesture corresponding to selection is a tap.

The device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI in touch screen 112.

In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, a Subscriber Identity Module (SIM) card slot 210, a head set jack 212, and a docking/charging external port 124. The push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval: to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, the device 100 also may accept verbal input for activation or deactivation of some functions through the microphone 113.

FIG. 3 is a block diagram of an exemplary computing device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a table 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 industrial controller). The device 300 typically includes one or more processing units (CPU's) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication buses 320 may include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. The device 300 includes an input/output (I/O) interface 330 comprising a touch screen display 112. The I/O interface 330 also may include a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355. Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include 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 may optionally include one or more storage devices remotely located from the CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in the memory 102 of portable multifunction device 100 (FIG. 1), or a subset thereof. Furthermore, memory 370 may store additional programs, modules, and data structures not present in the memory 102 of portable multifunction device 100. For example, memory 370 of device 300 may store drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1) may not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 370 may store a subset of the modules and data structures identified above. Furthermore, memory 370 may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“U”) that may be implemented on a portable multifunction device 100.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu of applications on a portable multifunction device 100 in accordance with some embodiments. Similar user interfaces may be implemented on device 300. In some embodiments, user interface 400A and/or 400B includes the following elements, or a subset or superset thereof:

- Signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals;
- Time 404;
- Bluetooth indicator 405;
- Battery status indicator 406;
- Tray 408 with icons for frequently used applications, such as:
  - Phone 138, which may include an indicator 414 of the number of missed calls or voicemail messages;
  - E-mail client 140, which may include an indicator 410 of the number of unread e-mails;
  - Browser 147; and
  - Music player 146; and
- Icons for other applications, such as:
  - IM 141;
  - Image management 144;
  - Camera 143;
  - Video player 145;
  - Weather 149-1;
  - Stocks 149-2;
  - Workout support 142;
  - Calendar 148;
  - Calculator 149-3;
  - Alarm clock 149-4;
  - Dictionary 149-5; and
  - User-created widget 149-6.

In some embodiments, user interface 400B includes the following elements, or a subset or superset thereof:

- 402, 404, 405, 406, 141, 148, 144, 143, 149-3, 149-2, 149-1, 149-4, 410, 414, 138, 140, and 147, as described above;
- Map 154;
- Notes 153;
- Settings 412, which provides access to settings for the device 100 and its various applications 136, as described further below;
- Video and music player module 152, also referred to as iPod (trademark of Apple, Inc.) module 152; and
- Online video module 155, also referred to as YouTube (trademark of Google, Inc.) module 155.

FIG. 4C illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112, FIG. 3) for resizing an array (e.g., 456) of a plurality of arrays (e.g., 454, 456 and 458) of user interface objects, without resizing another array (e.g., 454) of the plurality of arrays in response to an input from the user (e.g., enlarging the array in response to a depinch gesture that includes contacts 460 and 462 with the touch sensitive surface 451).

Although many of the examples which follow will be given with reference to inputs on a touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4C. In some embodiments the touch sensitive surface (e.g., 451 in FIG. 4C) has a primary axis (e.g., 452 in FIG. 4C) that corresponds to a primary axis (e.g., 453 in FIG. 4C) on the display (e.g., 450). In accordance with these embodiments, the device detects a plurality of simultaneous contacts (e.g., 460 and 462 in FIG. 4C) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4C, contact location 460 corresponds to location 468 on display 450 and contact location 462 corresponds to location 470 on display 450).

In the present example, as shown in FIG. 4C, locations (e.g., 468 and 470) on the display 450 that correspond to the simultaneous contacts (e.g., 460 and 462) are located proximate to one of the plurality of arrays (e.g., array 456) of user interface objects (e.g., images S1-S30) on the display (e.g., 450 in FIG. 4C). While continuing to detect the simultaneous user inputs, the device detects a depinching gesture including movement (e.g., 464 and 466) of at the simultaneous contacts (e.g., 460 and 462) on the touch-sensitive surface away from each other, which corresponds to a depinching gesture including corresponding movement (e.g., 472 and 474, respectively) of corresponding locations (e.g., 468 and 470, respectively) on the display away from each other. In response, the device expands the array (e.g., 456 in FIG. 4C) that is proximate to the locations (e.g., 470 and 472) which correspond to the contacts (e.g., 460 and 462) on the touch-sensitive surface (e.g., 451 in FIG. 4C). In this way, user inputs (e.g., contacts 460 and 462) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4C) are used by the device to manipulate user interface objects on the display (e.g., 450 in FIG. 4C) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods can be used for other user interfaces described herein.

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

Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a computing device with a touch screen display, such as device 300 or portable multifunction device 100.

FIGS. 5A-5Y illustrate exemplary user interfaces for moving one or more user interface objects to a destination object and performing an action associated with the destination object on the one or more user interface objects in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 9A-9D and 10A-11B.

FIGS. 5A-5G illustrate user interfaces for detecting a first user input (e.g., contact 5054, FIG. 5B) on a destination object (e.g., the label icon “Little Wesley” 5030); detecting a second user input on a user interface object (e.g., tap gesture 5056 on digital image D5 in FIG. 5C) while still detecting the first input; and performing an action associated with the destination object on the user interface object (e.g., giving image D5 the label “Little Wesley” 5030).

FIGS. 5G-5J illustrate user interfaces for undoing an action associated with a selected destination object (e.g., the label icon “Little Wesley” 5030) in response to detecting a user input on a residual image of the user interface object (e.g., shaded image D5 in FIG. 5H) while still detecting the first input (e.g., contact 5054). In response to detecting tap gesture 5066 in FIG. 5H on the residual image of D5, digital image D5 will not be given the label “Little Wesley” 5030 and image D5 replaces its residual image (FIG. 5J).

FIGS. 5J-5N illustrate user interfaces for performing a hide operation on a plurality of user interface objects (e.g., images B5 and B12) in an array 5060 of user interface objects in response to detecting user inputs (e.g., tap gestures 5072 (FIG. 5K) and 5076 (FIG. 5L)) on the user interface objects (B5 and B12) while continuing to detect a user input (e.g., contact 5070) on a destination object associated with a hide command (e.g., hide icon 5048).

FIGS. 5O-5T illustrate user interfaces for responding to detecting a user input (e.g., contact 5082) on a destination object (e.g., the label icon “Little Wesley” 5030) and then, while still detecting the user input on the destination object, detecting one or more user inputs (e.g., tap gesture 5084 in FIG. 5O, tap gesture 5088 in FIG. 5P, and swipe gesture with contact 5092 and movement 5094 in FIG. 5Q) on a plurality of user interface objects (e.g., digital images D11, D3, D6, D6, D12, D15, D18, D21, D24, D27, D30, D33, and D36) by performing an action associated with the destination object on the plurality of user interface objects (e.g., giving images D11, D3, D6, D6, D12, D15, D18, D21, D24, D27, D30, D33, and D36 the label “Little Wesley” 5030).

FIGS. 5T-5X illustrate user interfaces for responding to user inputs (e.g., tap gesture 5098 (FIG. 5T) and a swipe gesture that includes contact 5102 and movement 5104 of the contact (FIG. 5V)) on residual images of user interface objects (e.g., shaded images D3, D18, D21, D24, D27, D30, D33, D36 in FIG. 5T) by undoing an action associated with a destination object (e.g., the label icon “Little Wesley” 5030) while continuing to detect a user input (e.g., contact 5082) with the destination object. In response to detecting tap gesture 5098 (FIG. 5T) and the swipe gesture (FIG. 5V) on the residual images of D3. D18, D21, D24, D27, D30, D33, and D36, digital images D3, D18, D21, D24, D27, D30, D33, and D36 will not be given the label “Little Wesley” 5030 and images D3, D18, D21, D24, D27, D30, D33, and D36 replace their respective residual images (FIG. 5X).

FIGS. 5X-5Y illustrate a change in the user interface after performing an action associated with a destination object 5030 on a plurality of selected user interface objects (e.g., images D6, D9, D11, D12, D15) in response to ceasing the detect a user input (e.g., contact 5082 in FIG. 5X) on the destination object 5030. After the user releases contact 5082 with the icon 5030 in FIG. 5X, the device ceases to display the residual images of the user interface objects, and the original user interface objects are displayed in their initial user interface locations (FIG. 5Y). In this example, the residual images indicate to a user which images will be labeled “Little Wesley” when the device detects lift off of contact 5082. After lift off of contact 5082, the residual images are replaced with the original objects because all of the original objects D1-D36 and D7-r are still part of the “Day at the zoo” event.

FIGS. 6A-6X illustrate exemplary user interfaces for forming a group of user interface objects, moving the group to a destination object or an area associated with a destination object, and performing an action associated with the destination object on the group of user interface objects in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 11A-11B and 12A-12B.

FIGS. 6A-6G illustrate exemplary user interfaces for forming a group of two or more user interface objects by selecting a user interface object (e.g., image D27, FIG. 6B) from an array 6078 of user interface objects and dragging the selected object off of the array (e.g., in response to detecting contact 6052-1 in FIG. 6B with image D27 and movement 6054 of the contact off of the army in FIG. 6C). Subsequently, additional user interface objects (e.g., images D24 and D28) are grouped with the selected object in response to user inputs (e.g., tap gestures 6056 in FIG. 6D and 6062 in FIG. 6F) on the additional user interface objects.

FIGS. 6H-6I illustrate exemplary user interfaces for removing a user interface object (e.g., image D24) from the group of two or more user interface objects in response to detecting a user input (e.g., tap gesture 6066 in FIG. 6H) with a residual image of the user interface object (e.g., shaded image D24). In response to detecting tap gesture 6066 in FIG. 6H on the residual image of D24, digital image D24 is removed from the group of images (D27 and D28) and image D24 replaces its residual image (FIG. 6I).

FIGS. 6I-6M illustrate exemplary use interfaces for initiating performance of an action on the group of user interface objects (e.g., images D27 and D28). In FIG. 6J, in response to detecting a drag gesture that includes contact 6052 and movement 6070 to the Printer destination object 6042, printing of images D27 and D28 is initiated. In FIGS. 6K-6M, in response to detecting movement 6074 of the group to an area 6076 associated with destination object 6008, images D27 and D28 are made part of the array 6072 of images for the School garden event 6008.

FIGS. 6N-6Q illustrate exemplary user interfaces for forming a group of more than two user interface objects by selecting a user interface object (e.g., image D31, FIG. 6N) from an array 6078 of user interface objects and dragging the selected object off of the array (e.g., in response to detecting contact 6100-1 with image D31 and movement 6102 of the contact off of the array in FIG. 6N). Subsequently, additional user interface objects (e.g., images D10, D13, D16, D19, D22, D25, D30, D33, and D36) are grouped with the selected object in response to user inputs (e.g., a swipe gesture that includes contact 6104 and movement 6106 of the contact in FIG. 6O) on the additional user interface objects.

FIGS. 6Q-6S illustrate-exemplary user interfaces for removing a user interface object (e.g., image D25) from the group of more than two user interface objects in response to detecting a user input (e.g., tap gesture 6110 in FIG. 6Q) with a residual image of the user interface object (e.g., shaded image D25 in FIG. 6Q). In response to detecting tap gesture 6110 in FIG. 6Q on the residual image of D25, digital image D25 is removed from the group of images (D10, D13, D16, D19, D22, D30, D31, D33, and D36) and image D25 replaces its residual image (FIG. 6I).

FIGS. 6S-6X illustrate exemplary use interfaces for initiating performance of an action on the group of user interface objects (e.g., images D10, D13, D16, D19, D22, D30-D31, D33, and D36). In FIG. 6S, in response to detecting a drag gesture that includes contact 6100 and movement 6114 to the School garden event destination object 6008, images D10, D13, D16, D19, D22, D30, D31, D33, and D36 are made part of the array 6072 of images for the School garden event 6008 (FIG. 6X). In FIGS. 6T-6X, in response to detecting movement 6116 of the group to an area 6076 associated with destination object 6008, images D10, D13. D16, D19, D22, D30, D31, D33, and D36 are made part of the array 6072 of images for the School garden event 6008.

FIGS. 7A-7O illustrate exemplary user interfaces for zooming (e.g., zooming in) and rearranging user interface objects in an array with a multifinger gesture in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 13A-13B.

FIGS. 7A-7D illustrate exemplary user interfaces for zooming user interface objects (e.g., images S1-S41 in array 7002) in response to detecting a multifinger gesture (e.g., a depinching gesture made with contacts 7004 and 7006).

FIGS. 7D-71 illustrate exemplary user interfaces for rearranging user interface objects (e.g., images S1-S41) in response to detecting a release of user inputs (e.g., contacts 7004-2 and 7006-2 in FIG. 7D) after enlarging the array of user interface objects. Image S23, which was located at the centroid of the depinch gesture, is easy to locate after the rearrangement because it maintains its vertical position on the display.

FIGS. 7I-7J illustrate exemplary user interfaces for zooming (e.g., zooming out) user interface objects (e.g., images S1-S41 in array 7002) in response to detecting a multifinger gesture (e.g., a pinching gesture made with contacts 7016 and 7018).

FIGS. 7J-7K illustrate exemplary user interfaces for changing the vertical position of the array of user interface objects (e.g., images S I-S41 in array 7002) in response to detecting a vertical change in the position of the centroid (e.g., 7020) of a plurality of user inputs (e.g., contacts 7016 and 7018).

FIGS. 7K-7O illustrate exemplary user interfaces for rearranging user interface objects (e.g., images S1-S41) in response to detecting a release of user inputs (e.g., contacts 7016-3 and 7018-3 in FIG. 7K) after reducing the array of user interface objects. Image S9, which was located at the centroid of the pinch gesture, is easy to locate after the rearrangement because it maintains its vertical position on the display,

FIGS. 8A-8UU illustrate exemplary user interfaces for manipulating user interface objects in a plurality of arrays of user interface objects in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 14A-14I, 15A-15B, 16A-16B, and 17A-17B.

FIGS. 8A-8D illustrate exemplary user interfaces for vertically scrolling a plurality of arrays (e.g., arrays 8052, 8054, 8064, and 8066) of user interface objects in response to detecting a user input (e.g., a substantially vertical swipe gesture that includes contact 8060 and movement 8062 of the contact, FIG. 8B).

FIGS. 8D-8I illustrate exemplary user interfaces for horizontally scrolling an array (e.g., 8066) of user interface objects (e.g., images E1-E74) without scrolling the other arrays (e.g., arrays 8052, 8054, and 8064) of user interface objects in response to detecting a user input (e.g., a horizontal swipe gesture, such as contact 8070 and movement 8072 of the contact in FIG. 8D or contact 8080 and movement 8082 of the contact in FIG. 8G). FIGS. 8E-8F illustrate a rubber-band-like effect to indicate that the end of array 8066 is being displayed during detection of a horizontal scrolling gesture. FIGS. 8G-8H illustrate a rubber-band-like effect to indicate that the beginning of array 8066 is being displayed during detection of a horizontal scrolling gesture.

FIGS. 8I-8K illustrate exemplary user interfaces for scrolling a plurality of arrays (e.g., 8052, 8054, 8064 and 8066) to a particular array (e.g., 8052) in response to detecting a user input (e.g., tap gesture 8090 in FIG. 8I) on an array name icon (e.g., 8008) that is associated with the particular array (e.g., 8052).

FIGS. 8K-8P illustrate exemplary user interfaces for resizing one array (e.g., 8054) in the plurality of arrays, without resizing other arrays in the plurality of arrays in response to detecting an input from the user (e.g., enlarging array 8054 in response to detecting a depinch gesture that includes contacts 8096 and 8098 in FIG. 8K, or reducing the size of array 8054 in response to detecting a pinch gesture that includes contacts 8108 and 8110 in FIG. 8N).

FIGS. 8P-8R illustrate exemplary user interfaces for toggling the display of a representative user interface object (e.g., representative image S33-r) for an array (e.g., 8054) in response to detecting a user input on a representative user interface object toggle icon 8056 (e.g., tap gesture 8118 in FIG. 8P or a mouse click while a cursor 8120 is on the representative user interface object toggle icon 8056 in FIG. 8Q). These figures also illustrate exemplary user interfaces for rearranging the user interface objects (e.g., images S1-S41) concurrently with toggling the display of the representative user interface object.

FIGS. 8R-8V illustrate exemplary user interfaces for associating a user interface object (e.g., image D17) in a first array 8052 of user interface objects with a second array 8054 of user interface objects in response to detecting a user input (e.g., contact 8122 and movement 8124 of the contact to an area 8126 associated with the array 8054 in FIG. 8S) and subsequent cessation of the input. In this example, image D17 in the “Day at the zoo” event array 8052 is added to the “School garden” event array 8054.

FIGS. 8V-8AA illustrate exemplary user interfaces for selecting all of the user interface objects in an array (e.g., images D1-D16, D18-D36 in array 8052. FIG. 8V) in response to detecting a user input (e.g., contact 8130-1, FIG. 8V) on an array name icon (e.g., 8132) for the array. An action is performed on all of the selected user interface objects in response to detecting a user input (e.g., contact 8130 and movement 8132 of the contact to an area 8134 associated with the “Family reunion” event icon 8010 in FIG. 8X) and subsequent cessation of the input. In this example, all of the images from the “Day at the zoo” array 8052 are made part of the “Family reunion” array 8064, as illustrated in FIG. 8AA.

FIGS. 8AA-8DD illustrate exemplary user interfaces for displaying a plurality of representative user interface icons (e.g., representative images B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIGS. 8CC-8DD) in response to detecting activation (e.g., by tap gesture 8140 in FIG. 8AA) of a respective menu category icon (e.g., Events icon 8002 in FIG. 8AA).

FIGS. 8CC and 8EE illustrate exemplary user interfaces for responding to a user input (e.g., tap gesture 8142 in FIG. 8CC) on a representative user interface icon (e.g., representative image B1-r in FIG. 8CC for the Birthday array 8144) by displaying the corresponding array (e.g., 8144 in FIG. 8EE).

FIGS. 8FF-8JJ illustrate exemplary user interfaces for, while detecting a user input (e.g., contact 8146) with a destination object (e.g., “Adorable children” label icon 8032), responding to a user input (e.g., tap gesture 8148 in FIG. 8GG) on an array name icon (e.g., 8132) for an array (e.g., 8052) of user interface objects by performing an action associated with the destination object (e.g., 8032) on all of the user interface objects (e.g., images D1-D16, D18-D36) in the array 8052 of user interface objects). In this example, images D1-D16, D18-D36 in array 8052 would be given the label “Adorable children.”

FIGS. 8JJ-8LL illustrate exemplary user interfaces for undoing an action associated with a selected destination object (e.g., 8032) in response to detecting a user input (e.g., tap gesture 8150) on a residual image of a user interface object (e.g., shaded image D12 in FIG. 8JJ). In this example, image D12 will not be labeled “Adorable children” and the residual shaded image of D12 (FIG. 8JJ) is replaced by the original unshaded image of D12 (FIG. 8LL).

FIGS. 8MM-8NN illustrate exemplary user interfaces for responding to a plurality of user inputs with a plurality of destination objects (e.g., tap gestures 8158, 8160 and 8162 on icons 8006, 8008 and 8032, respectively), while continuing to detect a user input (e.g., contact 8154 in FIG. 8MM) with a user interface object (e.g., image B26), by performing plurality of actions (e.g., an action associated with each of the destination objects 8006, 8008 and 8032) on the user interface object (e.g., adding image B26 to the “Day at the zoo” array 8052 and the School garden array 8054 (FIG. 8NN), and adding the label “Adorable children” to image B26).

FIGS. 8NN-8QQ illustrate exemplary user interfaces for responding to a user input (e.g., double tap gesture 8164, FIG. 8NN) on a first user interface object (e.g., image D29) in an array (e.g., 8054) of user interface objects by displaying an enlarged representation of the first user interface object (e.g., image D29-f in FIG. 8OO), and then displaying an enlarged representation of a second user interface object (e.g., image D30-f in FIGS. 8PP-8QQ) that is adjacent to the first user interface object in the array in response to a user input (e.g., a swipe gesture that includes contact 8166 and movement 8168 of the contact, FIG. 8OO) on the enlarged representation of the first user interface object.

FIGS. 8OO and 8RR illustrate exemplary user interfaces for responding to a user input (e.g., press and hold gesture 8172 in FIG. 8OO) on an enlarged representation of a user interface object (e.g., image D29-f in FIG. 8OO) by displaying the enlarged representation of the user interface object (e.g., image D29-f in FIG. 8RR) in cover flow mode.

FIGS. 8SS-8UU illustrate exemplary user interfaces for responding to a user input (e.g., contact 8174 and subsequent movement 8176 of the contact in FIG. 8SS) on a user interface object (e.g., image D22) in an array (e.g., 8052) by replacing the current representative user interface object (e.g., representative image D7-r in FIG. 8SS) for the array (e.g. 8052) with a new representative user interface object (e.g., representative image D22-r in FIG. 8UU) that is a representation of the user interface object (e.g., image D22) on which the user input was detected.

FIGS. 9A-9D are flow diagrams illustrating a method 900 of moving one or more user interface objects to a destination object and performing an action associated with the destination object on the one or more user interface objects in accordance with some embodiments. The method 900 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 5A-5J). Some operations in method 900 may be combined and/or the order of some operations may be changed.

As described below, the method 900 provides an intuitive way to manipulate user interface objects in response to multiple simultaneous user inputs at a computing device with a touch screen display. The method reduces the cognitive burden on a user when providing instructions to perform an action on one or more of the user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to perform actions on one or more user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (902) on the touch screen display (e.g., 112 in FIG. 5A) a plurality of user interface objects (e.g., digital images B1-B27, B1-r and/or D1-D36, D7-r in FIG. 5A) and at least one destination object (e.g., icons 5004, 5006, 5008, 5010, 5012, 5014, 5016, 5018, 5020, 5022, 5024, 5028, 5030, 5032, 5034, 5038, 5040, 5042, 5044, 5046, 5048, and/or 5050 in FIG. 5A). The user interface objects are ‘selectable objects’ (i.e., objects configured to be selectable by a user).

In some embodiments, the user interface objects (e.g., B1-B27, B1-r, D1-D36-r, etc.) are (904) digital images (e.g., photographic images and/or digital graphics). In some embodiments, the user interface objects are (906) digital content (e.g., digital images, videos, music albums or individual tracks, audio books, and/or podcasts). In some embodiments, the user interface objects are (908) electronic documents (e.g., word processing, spreadsheets, and/or presentation documents). In some embodiments, the user interface objects are (910) folders (e.g., user interface objects that represent a collection of other user interface objects in a hierarchical directory). For example, if user interface object B1 is a folder in a hierarchical directory structure, then selection and activation of user interface object B1 will display the contents of the folder (e.g., user interface objects associated with files at a lower level in the hierarchical directory).

In some embodiments, the destination object (e.g., label icon 5030) is (912) operable to associate metadata with one or more of the user interface objects. In some embodiments, the metadata is (914) stored with the first user interface object upon performance of an action (e.g., the metadata is stored in a data structure that corresponds to the user interface object). In some embodiments, the metadata is (916) stored, upon performance of an action, in a data structure that is separate from a data structure that corresponds to the user interface object (e.g., in a data structure associated with the destination object).

In some embodiments, the metadata comprises a representation of an event (e.g., metadata corresponding to event icons 5004, 5006, 5008, 5010, 5012, 5014, 5016, 5018, 5020, 5022, and 5024 in FIG. 5A). For example, when the user interface objects are images, the event Birthday 5004 may be associated with a set of images (e.g., B1-B27). In some embodiments, events are mutually exclusive (e.g., a user interface object may be associated with at most a single event). In other words, in these embodiments, when a user interface object is already associated with a first event, if it is associated with a second event that is distinct from the first event, it ceases to be associated with the first event. In some embodiments, events are nonexclusive (e.g., a user interface object may be simultaneously associated with multiple distinct events).

In some embodiments, the metadata comprises (918) a label (e.g., a user-defined label or a user rating). For example, in FIG. 5A, where the user interface objects are images, the label “Little Wesley” 5030 is associated with a set of images that the user has given the label “Little Wesley” (in this example, it should be understood that, typically, these images will be the images that include a child named Wesley). In some embodiments, labels are nonexclusive (e.g., a user interface object may be simultaneously associated with multiple distinct labels).

In some embodiments, the destination object represents (920) a set of user interface objects (e.g., a set of user interface objects with a common label, such as Little Wesley 5030 in FIG. 5A). In some embodiments, the destination object represents (922) an electronic document (e.g., a slideshow 5038, an email message, a web site, a book, or a word processing document). In some embodiments, the destination object represents (924) a folder. In some embodiments, the destination object represents (926) an output device (e.g., a printer 5042 or a print service 5046). In some embodiments, the destination object is (928) displayed as a menu item (e.g., 5004-5024, 5028-5034, or 5038-5050) in a menu (e.g., a menu item in a sidebar menu 5052).

The device detects (930) a first input (e.g., contact 5054 in FIG. 5B) by a user on a destination object (e.g., “Little Wesley” 5030 in FIG. 5B). For example, the first input may include any of: a thumb or other finger contact, a stylus contact, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the destination icon. In some embodiments, the destination object is in a list of destination objects (e.g., a menu item in a sidebar menu 5052 or palette, which is easy to select with a thumb). For example, in FIG. 53, the menu 5052 is located along the left side of the touch screen display 112, and thus for a user holding the computing device in two hands, the thumb of the left hand will typically be naturally positioned near the sidebar menu 5052.

Operations 934-966 are performed while the device continues (932) to detect the first input (e.g., contact 5054 in FIGS. 5B-5I) by the user on the destination object (e.g., “Little Wesley” 5030 in FIGS. 5B-5I).

The device detects (934) a second input (e.g., contact 5056 in FIG. 5C) by the user (e.g., a finger gesture such as a tap gesture, a stylus contact, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the first user interface object) on a first user interface object (e.g., user interface object D5 in FIG. 5C) displayed at an initial first user interface object position on the touch screen display. If the first and second inputs are finger gestures, the finger that makes the first input is different from the finger that makes the second input (e.g., contact 5054 is a contact from the thumb of the left hand and contact 5056 is a contact from an index finger of the right hand of the user). The destination object (e.g., “Little Wesley” 5030 in FIG. 5C) is different from the first user interface object (e.g., D5 in FIG. 5C).

In some embodiments, the second input by the user is (936) a tap input (e.g., a tap gesture including contact 5056 and release of the contact). In some embodiments, the second input is a finger gesture and the response to the second finger gesture is initiated when a finger-down event (e.g., 5056 in FIG. 5C) in the second finger gesture is detected. In some embodiments, the response to the second finger gesture is initiated when a finger-up event in the second finger gesture is detected (e.g., when contact 5056 in FIG. 5C ceases to be detected, as described below with reference to FIG. 5F).

In some embodiments, the second input by the user is (938) a finger swipe gesture (e.g., contact 5058 and subsequent movement 5060 across the touch screen in FIG. 5D) that contacts the first user interface object (e.g., image D5 in FIG. 5D).

In response to detecting the second input (e.g. contact 5056 in FIG. 5C) by the user on the first user interface object (e.g., 5D in FIG. 5C), the device performs (940) an action on the first user interface object. The action is associated with the destination object. For example, when the destination object is a label (e.g., “Little Wesley” 5030 in FIG. 5C) and the first user interface object (e.g., D5 in FIG. 5C) is an image, the action is to associate the label with the image (e.g., store the label in metadata associated with the image). In some embodiments, the action is a preparatory action, such as preparing to perform an action that will occur upon detecting lift off of the first input (e.g., lift off of a first finger contact by the user) from the destination object. Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document.

In some embodiments, the destination object corresponds (942) to a set of objects and the action performed is adding or preparing to add the first user interface object to the set of objects. For example, if the first contact was with a menu item that is representative of an event (e.g., “Birthday” icon 5004 in FIG. 5D), then the action performed is adding or preparing to add the first user interface object (e.g., D5 in FIG. 5D) to the “Birthday” event. In some embodiments, the destination object (e.g., “Birthday” icon 5004) corresponds (944) to an array (e.g., 5060 in FIG. 5D) of objects (e.g., B1-B27 and B1-r) and the action performed is adding or preparing to add the first user interface object (e.g., D5 in FIG. 5D) to the array (e.g., 5060 in FIG. 5D) of objects (e.g., B1-B27 and B1-r). In some embodiments, the destination object corresponds (946) to a grid of objects and the action performed is adding or preparing to add the first user interface object to the grid of objects. For example, in FIG. 5D, user interface objects B1-B27 are arranged in a three by nine array of user interface objects.

In some embodiments, the destination object corresponds (948) to a folder and the action performed is adding or preparing to add the first user interface object to the folder. In some embodiments, the destination object corresponds (950) to a label (e.g., “Little Wesley” 5030 in FIG. 5D) and the action performed is adding or preparing to add the label (e.g., “Little Wesley”) to the first user interface object (e.g., D5 in FIG. 5D).

In some embodiments, the destination object corresponds (952) to a hide label (e.g., 5048 in FIG. 5D) and the action performed is adding or preparing to add the hide label to the first user interface object (e.g., D5 in FIG. 5D) and ceasing to display or preparing to cease to display the first user interface object. In some embodiments, a residual image of each object (e.g., a shaded or semitransparent image of each original object) to be hidden is displayed until lift off of the first input (e.g., lift off of the first finger contact 5030 by the user) is detected, at which point display of the residual image(s) ceases and remaining unhidden user interface objects in the array are rearranged to fill the spaces left by the hidden objects (e.g., as described in greater detail below with reference to FIGS. 5J-5N, except in the present example only a single object would be hidden instead of the multiple objects which are hidden in FIGS. 53-5N).

In some embodiments, the destination object (e.g., 5042 or 5046 in FIG. 5A) corresponds (954) to an output device (e.g., a printer, a print service or a fax, etc.) and the action performed is sending the first user interface object (e.g., D5 in FIG. 5D) to the output device. For example, when the user interface object is an image, and the destination object is a printer, upon detecting the second input by the user, the device will print (or prepare to print) the image on a printer associated with the device.

In some embodiments, in response to detecting the second input by the user on the first user interface object, the device displays (956) an animation of the first user interface object moving from the initial first user interface object position into the destination object. For example, FIG. 5E illustrates an animation of user interface object D5 moving from the initial first user interface object position into the destination object “Little Wesley” 5030. In this animation the user interface object D5 moves along a path (e.g., 5062 in FIG. 5E) from the initial location at D5 to the destination object 5030. In one embodiment, as the first user interface object moves along the path, the user interface object is resized so as to match the size of the destination object. An illustrative example of the movement and resizing (e.g., from D5, to D5′, to D5″, to D5′″, and finally to D5″″ in FIG. 5E) of the destination object is shown in FIG. 5E, in this example, the destination object 5030 is larger along the horizontal dimension (i.e., longer) and smaller along the vertical dimension (i.e., shorter) than the first user interface object D5. Thus, as illustrated in FIG. 5E, the user interface object D5 is stretched horizontally and compressed vertically as it moves (e.g., from D5, to D5′, to D5″, to D5′″ and finally to D5″″ in FIG. 5E) towards the destination object 5030. It should be understood that, typically the various resized representations of the user interface object (e.g., D5, D5′, D5″, D5′″ and D5″″ in FIG. 5E) are not simultaneously displayed, but are instead displayed in sequence as the user interface object moves along the path 5062 towards the destination object. In some embodiments, where the user interface object includes an image, the image is distorted as the object is resized. The animation indicates to a user that an action associated with the destination object will be applied to the first user interface object.

In some embodiments, when the second input is a finger gesture, the animation and the response to the finger gesture are initiated when a finger-up event in the finger gesture is detected (e.g., when contact 5056 in FIG. 5C ceases to be detected, as shown in FIG. 5F). For example, FIG. 5F illustrates an animation of user interface object D5 moving from the initial first user interface object position into the destination object “Little Wesley” 5030. In this animation, the user interface object D5 moves along a path (e.g., 5064 in FIG. 5F) from the initial location at D5 to the destination object 5030, as described above for FIG. 5E. In this embodiment, the animation is displayed when the finger lift off is detected (e.g., a finger-up event) from a user interface object rather than when finger contact on the user interface object is detected (e.g., a finger-down event). In some embodiments, the lift-off contact position is distinct from the initial contact position (e.g., set-down position). This embodiment may be used where the user interface objects are small relative to the size of the finger contact because the user is able to more accurately determine the lift-off position of the contact than the initial contact position (e.g., set-down position).

In some embodiments, while still detecting the first input (e.g., contact 5054 in FIG. 5O) with the destination object (e.g., “Little Wesley” 5030 in FIG. 5O), in response to detecting the second input by the user on the first user interface object, the device displays (958) a residual image of the first user interface object (e.g., shaded user interface object D5 in FIG. 5O) at the initial first user interface object position on the touch screen display. In some embodiments, the residual image (e.g., shaded user interface object D5 in FIG. 5G) is an image of the first user interface object with reduced opacity (e.g., a semitransparent or transparent image of the first user interface object). In some embodiments, the residual image of the first user interface object is (960) visually distinct from the first user interface object. In some embodiments, the residual image of the first user interface object is (962) a grayed-out, translucent, semi-transparent, reduced contrast, or ghost image of the first user interface object.

In some embodiments, the device detects (964) a third input by the user (e.g., a finger gesture such as a tap gesture 5066 in FIG. 5H, a stylus tap gesture, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the residual image of the first user interface object) on the residual image (e.g., shaded user interface object D5 in FIG. 5H) of the first user interface object at the initial first user interface object position on the touch screen display while continuing to detect the first input (e.g., contact 5054 in FIG. 5H) by the user on the destination object (e.g., “Little Wesley” 5030 in FIG. 5H). In response to detecting the third finger input (e.g., tap gesture 5066 in FIG. 5H) by the user on the residual image (e.g., shaded D5 in FIG. 5) of the first user interface object at the initial first user interface object position on the touch screen display, the device undoes the action performed on the first user interface object and displays the first user interface object at the initial first user interface object position. For example, user interface object D5 will not be labeled “Little Wesley” and the residual shaded image of D5 (FIG. 5H) is replaced by the original unshaded image of D5 (FIG. 5J).

In some embodiments, in response to detecting the third finger input (e.g., tap gesture 5066) by the user on the residual image (e.g., shaded image D5 in FIG. 5H) of the first user interface object at the initial first user interface object position on the touch screen display, the device displays (966) an animation of the first user interface object moving from the destination object back to the initial first user interface object position. The animation indicates to a user that an action associated with the destination object will not be applied to the respective user interface object. For example, FIG. 5I illustrates an exemplary animation of undoing the prior movement of user interface object D5 from the initial first user interface object position into the destination object “Little Wesley” 5030 (as shown in FIGS. 5E and 5F). In this animation, the user interface object D5 moves along a path (e.g., 5068 in FIG. 5I) from an initial location at the destination object 5030 to the original position of the first user interface object (e.g., D5 in FIG. 5I). In one embodiment, as the first user interface object moves along the path, the user interface object is initially displayed as a resized representation so as to match the size of the destination object. An illustrative example of the movement and resizing (e.g., from D5″″ to D5′″ to D5″ to D5′ in FIG. 5I and finally to D5 in FIG. 5J) of the destination object is shown in FIGS. 5I-5J. In this example, destination object 5030 is larger along the horizontal dimension (i.e., longer) and smaller along the vertical dimension (i.e., shorter) than the first user interface object D5. Thus, as illustrated in FIG. 5I, the user interface object is initially displayed as a representation of the user interface object (e.g., D5″″) that is stretched horizontally and compressed vertically compared to the original user interface object (e.g., D5). As the user interface object moves (e.g., from D5″″ to D5′″ to D5″ to D5′ and finally to D5) towards the original position of the user interface object D5 the user interface object is compressed horizontally and stretched vertically so that it returns to the dimensions of the original user interface object D5. It should be understood that, typically the various resized representations of the user interface object (e.g., D5, D5′, D5″, D5′″ and D5′″ shown in FIG. 5I) are not simultaneously displayed, but are instead displayed in sequence as the user interface object moves along the path 5068 towards the initial first user interface object position. In some embodiments, where the user interface object includes an image, the image is distorted as the object is resized.

After the device undoes the action performed on the first user interface object, the first user interface object is displayed at the initial first user interface object position, (e.g., image D5, as shown in FIG. 5J).

Note that details of the processes described above with respect to method 900 (e.g., FIGS. 9A-9D) are also applicable in an analogous manner to the methods described below. For example, the user interface objects and destination objects described below may have one or more of the characteristics of the user interface objects and destination objects described with reference to method 900. For brevity, these details are not repeated below.

FIGS. 10A-10B are flow diagrams illustrating a method 1000 of moving multiple user interface objects to a destination object and performing an action associated with the destination object on the multiple user interface objects in accordance with some embodiments. The method 1000 is performed at a computing device (e.g., device 300. FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 5J-5Y. Some operations in method 1000 may be combined and/or the order of some operations may be changed.

As described below, the method 1000 provides an intuitive way to manipulate a plurality of user interface objects at a computing device with a touch screen display. The method reduces the cognitive burden on a user when simultaneously manipulating a plurality of user interface objects using simultaneous user inputs, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1002) on the touch screen display (e.g., 112 in FIG. 5J) a plurality of user interface objects (e.g., digital images B1-B27, B1-r and/or D1-D36, D7-r in FIG. 5J) and at least one destination object (e.g., icons 5004, 5006, 5008, 5010, 5012, 5014, 5016, 5018, 5020, 5022, 5024, 5028, 5030, 5032, 5034, 5038, 5040, 5042, 5044, 5046, 5048, and/or 5050 in FIG. 5J). In some embodiments, the user interface objects are ‘selectable objects’ (i.e., objects configured to be selectable by a user).

The device detects (1004) a first input by a user on a destination object (e.g., a thumb or other finger contact, a stylus contact, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the destination icon). In some embodiments, the destination object is in a list of destination objects (e.g., a menu item in a sidebar menu or palette, which is easy to select with a thumb).

Operations 1008-1018 are performed while the device continues (1006) to detect the first input by the user on the destination object (e.g., contact 5070 on “Hide” icon 5048 in FIGS. 5J-5M or contact 5082 with “Little Wesley” label icon 5030 in FIGS. 5O-5X).

The device detects (1008) a second input by the user or a series of inputs by the user on two or more user interface objects in the plurality of user interface objects. The two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display. If both inputs are finger inputs, the finger that makes the first input (e.g., the first finger contact by the user) is different from the finger that makes the second input or series of inputs. For example, the device detects a series of tap gestures (e.g., tap gestures 5084 and 5088 as shown in FIGS. 50 and 5P, respectively) with a finger or stylus or a series of mouse clicks on the two or more user interface objects, a swipe gesture (e.g., contact 5092-1 and movement 5094 of the contact as shown in FIGS. 5Q-5R) with a finger or stylus that contacts the two or more user interface objects, or multiple simultaneous finger gestures (such as concurrent finger contacts on the two or more user interface objects).

In response to detecting the second input by the user or series of inputs by the user on the two or more user interface objects, the device performs (1010) an action on each of the two or more user interface objects. The action is associated with the destination object. In some embodiments, the action is a preparatory action, such as preparing to perform an action that will occur upon detecting lift off of the first input (e.g., lift off of the first finger contact by the user) from the destination object.

In some embodiments, in response to detecting the second input by the user or series of inputs by the user on the two or more user interface objects, the device displays (1012) animations (e.g. as described in greater detail below with reference to FIGS. 5K, 5L and 5R) of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position into the destination object. The animations indicate to a user that an action associated with the destination object will be applied to the respective user interface objects.

In some embodiments, in response to detecting the second input by the user or series of inputs by the user on the two or more user interface objects, the device displays (1014) a residual image (e.g., shaded user interface objects B5 and B12 in FIG. 5M, as described in greater detail below) for each of the two or more user interface objects at a respective initial user interface object position on the touch screen display.

For example, in FIG. 5J, the device detects a first input (e.g., contact 5070) by the user on a destination object (e.g., “Hide” icon 5048). In this example, the device detects a second input by the user (e.g., tap gesture 5072 in FIG. 5J) or a series of inputs (e.g., tap gesture 5072 in FIG. 5J followed by tap gesture 5076 in FIG. 5L) by the user on two or more user interface objects in the plurality of user interface objects. The two or more user interface objects (e.g., B5 and B12 in FIG. 5J) are displayed at respective initial user interface object positions on the touch screen display. In this example, in response to detecting each of the second inputs (e.g., contacts 5072 in FIG. 5K and 5076 in FIG. 5L) by the user on the two or more user interface objects, the device performs an action on each of the two or more user interface objects. The action is associated with the destination object. In some embodiments, the action is a preparatory action, such as preparing to hide the user interface objects upon detecting lift off of the first input (e.g., lift off of the first finger contact 5070 by the user) from the destination object (e.g., “Hide” 5048 in FIG. 5M).

In this example, in response to detecting tap gesture 5072, the device displays an animation showing user interface object B5 resizing (e.g., from B5, to B5′, to B5″, to B5′″, and finally to B5″″ in FIG. 5K) and moving towards or into the destination object (e.g., “Hide” icon 5048 in FIG. 5K) along a path 5074 from the initial user interface object B5 location to the destination object 5048. Similarly, in response to detecting tap gesture 5076, the device displays an animation showing user interface object B12 resizing (e.g., from B12, to B12′, to B12″, to 1312′″, and finally to B12″″ in FIG. 5L) and moving towards or into the destination object (e.g., “Hide” icon 5048 in FIG. 5L) along a path 5078 from the initial user interface object location to the destination object.

In this example, while the device continues to detect the first user input (e.g., contact 5070 in FIG. 5M) with the destination object (e.g., “Hide” icon 5048 in FIG. 5M), the device displays a residual image for each of the two or more user interface objects (e.g., shaded user interface objects D5 and D12 in FIG. 5M) at a respective initial user interface object position on the touch screen display. In this example, when the device ceases to detect the first user input (e.g., when the device detects lift-off of contact 5070 in FIG. 5M) the device performs the action by hiding the user interface objects (e.g., the device ceases to display the residual images for the two or more user interface objects B5 and B12 and rearranges the remaining unhidden user interface objects in the array so as to fill in the spaces left by the hidden objects. Thus, as shown in FIG. 5N, the user interface objects that the user selected while simultaneously selecting the “Hide” destination object (e.g., B5 and B12) are not displayed in the “Birthday” array (e.g., 5060 in FIG. 5N).

As described in greater detail below with reference to FIGS. 8A-8D, in some embodiments the user interface is scrolled so that different user interface items are displayed. For example, in FIG. 5N, the device scrolls 5080 the user interface items upwards, so that new user interface objects (e.g., S1-S39, and S33-r in FIG. 5O) are displayed and old user interface objects (e.g., B1-B27 in the “Birthday” array 5060) are no longer displayed.

As another example of selecting multiple user interface objects, in FIG. 5O, the device detects a first input (e.g., contact 5082) by the user on a destination object (e.g., “Little Wesley” 5030). In this example, the device detects a second input by the user (e.g., 5084 in FIG. 5O) or a series of inputs (e.g., tap gesture 5084 in FIG. 5O followed by tap gesture 8088 in FIG. 5P and swipe gesture including contact 5092-1 and subsequent movement 5094 of the contact in FIG. 5Q to contact location 5092-2 in FIG. 5R) by the user on two or more user interface objects in the plurality of user interface objects. The two or more user interface objects (e.g., D3 in FIG. 5O, D11 in FIG. 5P and D6, D9, D12, D15, D18, D21, D24, D30, D33, D36 in FIG. 5Q) are displayed at respective initial user interface object positions on the touch screen display. In this example, in response to detecting each of the second inputs by the user (e.g., contact 5084 in FIG. 5O followed by contact 8088 in FIG. 5P and swipe gesture including contact 5092-1 and subsequent movement 5094 of the contact in FIG. 5Q), the device performs an action on each of the two or more user interface objects. The action is associated with the destination object (e.g., “Little Wesley” 5030 in FIGS. 5O-5Q). In some embodiments, the action is a preparatory action, such as preparing to add a label “Little Wesley” 5030 to the selected user interface objects upon detecting lift off of the first input (e.g., lift off of the first finger contact by the user) from the destination object (e.g., “Little Wesley” 5030 in FIGS. 5O-5Q).

In this example, in response to detecting contact 5084, the device displays an animation showing user interface object D3 resizing (e.g., from D3, to D3′, to D3″, to D3′″, and finally to D″″ in FIG. 5O) and moving towards or into the destination object (e.g., “Little Wesley” 5030 in FIG. 5O) along a path 5086 from the initial user interface object D3 location to the destination object 5030. Similarly, in response to detecting contact 5088, the device displays an animation showing user interface object D11 resizing (e.g., from D11, to D11′, to D11″, to D11′″, and finally to D11″″ in FIG. 5P) and moving towards or into the destination object (e.g., “Little Wesley” 5030 in FIG. 5P) along a path 5090 from the initial user interface object D11 location to the destination object 5030.

The device also displays an animation in response to detecting the swipe gesture (e.g., contact 5092-1 and subsequent movement 5094 of the contact in FIG. 5Q to contact location 5092-2 in FIG. 5R) on D6, D9, D12, D15, D18, D21, D24, D30, D33, D36 in FIG. 5Q by showing some or all of the user interface objects D6, D9, D12, D15, D18, D21, D24, D30, D33, D36 resizing and moving towards or into the destination object 5030. For illustrative purposes, respective user interface objects D18″″, D21′, D24′″, D27″, D30″, D33′ and D36′ are each shown moving from their respective initial positions towards the destination object (e.g., “Little Wesley” 5030 in FIG. 5Q) along a respective path (e.g., 5096 for user interface object D36) from the initial user interface object location for the respective user interface object to the destination object.

In this example, while the device continues to detect the first user input (e.g., contact 5082 in FIG. 5S) with the destination object (e.g., “Little Wesley” 5030 in FIG. 5S), the device displays a residual image for each of the two or more user interface objects (e.g., shaded user interface objects D3, D6, D9, D11, D12, D15, D18, D21, D24, D27, D30, D33, D36 in FIG. 5S) at a respective initial user interface object position on the touch screen display. In this example, when the device ceases to detect the first user input (e.g., when the device detects lift-off of contact 5082 in FIG. 5S), the device performs the action by adding the label “Little Wesley” to the metadata of the user interface objects that were selected by the user (e.g., D3, D6, D9, D11, D12, D15, D18, D21, D24, D27, D30, D33, D36 in FIG. 5S).

In some embodiments, the device detects (1016) a third input by the user (e.g., a finger gesture such as a tap gesture 5098 on the residual image of D3 in FIG. 5T: a finger swipe gesture with contact 5102-1 and movement 5104 of the contact over the residual images of D18, D21, D24, D27, D30, D33, and D36 in FIG. 5V; a stylus tap gesture; or a mouse input such as a mouse click when a cursor controlled by the mouse is over a respective residual image of a respective user interface object) on a respective residual image of a respective user interface object at a respective initial user interface object position on the touch screen display while continuing to detect the first input by the user on the destination object (e.g., contact 5082 on icon 5030). In response to detecting the third input by the user on the respective residual image of the respective user interface object at the respective initial user interface object position on the touch screen display, the device undoes the action performed on the respective user interface object and displays the respective user interface object at the respective initial user interface object position. For example, user interface objects D3, D18, D21, D24, D27, D30, D33, and D36 will not be labeled “Little Wesley” and the residual shaded images of D3, D18, D21, D24, D27. D30, D33, and D36 (FIG. 5S) are replaced by the original unshaded images of D3, D18. D21, D24, D27, D30, D33, and D36 (FIG. 5X).

In some embodiments, the device displays (1018) an animation of the respective user interface object moving from the destination object back to the respective initial user interface object position (e.g., as shown in FIGS. 5U and 5W, and described in greater detail below). The animation indicates to a user that an action associated with the destination object will not be applied to the respective user interface object.

For example, in FIG. 5T the device detects a third user input (e.g., tap gesture 5098) on the residual image of D3 (e.g., shaded user interface object D3 in FIG. 5T). In response to detecting the tap gesture 5098, the device undoes the action performed on the respective user interface object and displays an animation of the respective user interface object moving from the destination object (e.g., “Little Wesley” 5030 in FIG. 5U) back to the initial user interface object position D3. In this example, the device displays an animation showing user interface object (e.g., D3″″) that is stretched horizontally and compressed vertically compared to the original user interface object (e.g., D3). As the user interface object moves (e.g., from D3″″ to D3′″ to D3″ to D3) along a path 5100 from the destination object location (e.g., “Little Wesley” 5030 in FIG. 5U) towards the original position of the user interface object D3 the user interface object is compressed horizontally and stretched vertically so that it returns to the dimensions of the original user interface object D3. As shown in FIG. 5V, the device displays the respective user interface object (e.g., unshaded user interface object D3 in FIG. 5V) at the respective initial user interface object position.

Similarly, in some embodiments, in response to a swipe gesture that includes contact with a plurality of residual images of user interface objects, the device will undo the action performed on the plurality of respective user interface object associated with the residual images of the user interface objects. For example, in FIG. 5V the device detects a third user input (e.g., contact 5102-1 and movement 5104 in FIG. 5V of the contact to location 5102-2 in FIG. 7W) on the residual images of D18, D21. D24, D27, D30, D33 and D36. In response to detecting the swipe gesture, the device undoes the action performed on the respective user interface objects and displays an animation of the respective user interface objects moving from the destination object (e.g., “Little Wesley” 5030 in FIG. 5W) back to their respective initial user interface object positions. In this example, the device displays an animation showing some or all of the user interface objects (e.g., D18, D21 D24, D30, D33, D36) resizing and moving. For illustrative purposes, exemplary user interface objects D36′″, D33″, D30″, and D27 are shown moving from the destination object (e.g., “Little Wesley” 5030 in FIG. 5W) to their respective initial positions along respective paths (e.g., 5106 for user interface object D36). In FIG. 5W, user interface objects D18. D21 and D24 are shown as having already been returned to their respective initial positions. In some embodiments, the movement and resizing of each of these user interface objects is performed in accordance with the animation for moving and resizing user interface object D3 as described previously with reference to FIG. 5U.

In some embodiments, after the device undoes the action performed on the respective user interface objects (e.g., D18, D21, D24, D30, D33, and D36 in FIG. 5W), the device displays the respective user interface object at the respective initial user interface object position, as shown in FIG. 5X. In some embodiments, after the user releases the first contact (e.g., contact 5082 in FIG. 5X) with the destination object (e.g., icon 5030 in FIG. 5X), the device ceases to display the residual images of the user interface objects, and the original user interface objects are displayed (e.g., as shown in FIG. 5Y) in their initial user interface locations. In this example, the residual images indicate to a user which images will be labeled “Little Wesley” when the device detects lift off of contact 5082. After lift off of contact 5082, the residual images are replaced with the original objects because all of the original objects D1-D36 and D7-r are still part of the “Day at the zoo” event.

FIGS. 11A-11B are flow diagrams illustrating a method 1100 of forming a group of user interface objects, moving the group to a destination object or an area associated with a destination object, and performing an action associated with the destination object on the group of user interface objects in accordance with some embodiments. The method 1100 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 6A-6M). Some operations in method 1100 may be combined and/or the order of some operations may be changed.

As described below, the method 1100 provides an intuitive way to form and manipulate a group of user interface objects and perform actions on the group of user interface objects at a computing device with a touch screen display. The method reduces the cognitive burden on a user when manipulating a plurality of user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1102) on the touch screen display (e.g., 112 in FIG. 6A) a plurality of user interface objects (e.g., digital images D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, D13, D14, D15, D16, D17, D18, D19, D20, D21, D22, D23, D24, D25, D26, D27, D28, D29, D30, D31, D32, D33, D34, D35, D36, D7-r, and/or S1, S2, S3, S4, S5, S6, S7, S8, S9, S10, S11, S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S25, S26, S27, S28, S29, S30, S31, S32, S33, S34, S35, S36, S37, S38, S39, S33-r in FIG. 6A) and at least one destination object (e.g., icons 6004, 6006, 6008, 6010, 6012, 6014, 6016, 6018, 6020, 6022, 6024, 6028, 6030, 6032, 6034, 6038, 6040, 6042, 6044, 6046, 6048, and/or 6050 in FIG. 6A). In some embodiments, the user interface objects are ‘selectable objects’ (i.e., objects configured to be selectable by a user).

The device detects (1104) a first input by a user (e.g., a press and hold finger contact 6052 (FIG. 6B), stylus contact, or mouse click) on a first user interface object (e.g., image D27) at a first location on the touch screen display.

Operations 1108-1126 are performed while the device continues (1106) to detect the first input (e.g., contact 6052 in FIGS. 6B-6L) by the user.

The device detects (1108) movement of the first input by the user across the touch screen display to a second location on the touch screen display. For example, as shown in FIG. 6C, the device detects movement of a finger contact 6052 from a first location 6052-1 that corresponds to the initial position of user interface object D27 to a second location 6052-2 on the touch screen display.

The device moves (1110) the first user interface object in accordance with the movement 6054 of the first input by the user across the touch screen display to (or proximate to) the second location on the touch screen display. For example, as shown in FIG. 6C, the device moves the user interface object D27 from an initial location to a second location D27′ on the user interface that is proximate to the location 6052-2 of the contact.

The device detects (1112) a second input by the user (e.g., a finger gesture such as a tap gesture 6056 in FIG. 6D, a stylus contact, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the second user interface object) on a second user interface object (e.g., D24 in FIG. 6D) displayed at an initial second user interface object position on the touch screen display.

In response to detecting the second input by the user on the second user interface object, the device displays (1114) an animation of the second user interface object moving 6058 from the initial second user interface object position (e.g., D24 in FIG. 5B) to (or proximate to) the second location (e.g., proximate to the location of the contact 6052-2 in FIG. 6E). The animation may move the second user interface object to, proximate to, or into the first user interface object (e.g., D27′ in FIG. 6E). For example, in FIG. 6E, the second user interface object (e.g., D24′) is shown moving towards the first user interface object (e.g., D27′). The animation indicates to a user that the second user interface object is being grouped with the first user interface object.

In some embodiments, the device displays (1116) a counter (e.g., 6060 in FIG. 6E) of the number of user interface objects that have moved to the second location (e.g., in response to detecting the second input by the user on the second user interface object). In the example above, as the device is animating the movement of the second user interface object to the first user interface object, the device displays a counter to “2” (e.g., 6060-a in FIG. 6E) to indicate that two user interface objects (e.g., D27 and D24) have moved to the second location.

In some embodiments, in response to detecting the second input (e.g., tap gesture 6056 in FIG. 6D) by the user on the second user interface object, the device displays (1118) a residual image (e.g., shaded user interface object D24 in FIG. 6E) of the second user interface object at the initial second user interface object position on the touch screen display.

It should be understood that selecting a second user interface object, as described above can be repeated for any number of user interface objects, and in some embodiments, as each user interface object is selected, an animation is displayed and the counter increases to the number of selected user interface objects. For example, in FIG. 6F the device detects another input by the user (e.g., a finger gesture such as a tap gesture 6062 in FIG. 6F, a stylus contact, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the user interface object) on another user interface object (e.g., D28 in FIG. 6F) displayed at an initial user interface object position on the touch screen display. In response to detecting this input by the user on the user interface object, the device displays an animation of the user interface object moving (e.g., 6064 in FIG. 6G) from the initial user interface object position (e.g., D28 in FIG. 6F) to (or proximate to) the second location (e.g., the location of the contact 6052-2 in FIG. 6G). The animation may move the user interface object to, proximate to, or into the first user interface object (e.g., D27′ in FIG. 6G). For example, in FIG. 6G, a representation of the user interface object D28′ is shown moving towards the first user interface object (e.g., D27′). In some embodiments, the device displays a counter (e.g., 6060 in FIG. 6G) of the number of user interface objects that have moved to the second location (e.g., in response to detecting the input(s) by the user on one or more second user interface objects). In the example above, as the device is animating the movement of the user interface object D28 to the first user interface object, the device increments a counter to “3” (e.g., 6060-b in FIG. 6G) to indicate that three user interface objects (e.g., D27, D24 and D28) have moved to the second location.

In some embodiments, the device detects (1120) a third input by the user (e.g., a finger gesture such as a tap gesture 6066 in FIG. 6H, a stylus tap gesture, or a mouse input such as a mouse click when a cursor controlled by the mouse is over the residual image of the second user interface object) on the residual image of the second user interface object (e.g., shaded user interface object D24 in FIG. 6H) at the initial second user interface object position on the touch screen display while continuing to detect the first input by the user (e.g., contact 605-2, FIG. 6H). In response to detecting the third finger input by the user on the residual image of the second user interface object at the initial second user interface object position on the touch screen display, the device displays the second user interface object at the initial second user interface object position (e.g., unshaded user interface object D24 in FIG. 6I).

In some embodiments, the device displays (1122) an animation of the second user interface object moving (e.g., movement 6068 in FIG. 6H) from the second location back to the initial second user interface object position. The animation indicates to a user that the second user interface object is being removed from the group of objects at the second location. The animation may move the second user interface object from or out of the first user interface object. For example, in FIG. 6H, a representation of the second user interface object (e.g., D24′) is shown moving from the first user interface object (e.g., D27 in FIG. 6H) towards the initial position of the second user interface object (e.g., D24 in FIG. 6H). In some embodiments, the device displays a counter (e.g., 6060-c in FIG. 6H) of the number of user interface objects that are still located at the second location. In the example above, as the device is animating the movement of the second user interface object D24′ towards the initial second user interface object position on the touch screen, the device decrements a counter to “2” (e.g., 6060-c in FIG. 6H) to indicate that only two user interface objects (e.g., D27 and D28) remain in the second location. It should be understood that only two user interface objects “remain” at a location because three user interface objects (e.g., D27, D24 and D28) have moved to the location and one (e.g., D24) has moved away from the location. Thus, as described in the example above, in FIG. 6I the original user interface object D24 is displayed in its original location.

In some embodiments, the device detects (1124) movement of the first input (e.g., movement 6070 in FIG. 6J, which includes movement of contact 6052 from contact location 6052-2 to contact location 6052-3, to contact location 6052-4, to contact location 6052-5) by the user across the touch screen display from the second location (e.g., 6052-2) to a destination object (e.g., “Printer” object 6042 in FIG. 6J) or an area associated with a destination object. The device moves the first user interface object and the second user interface object in accordance with the movement of the first input by the user across the touch screen display to the destination object or the area associated with a destination object (e.g., movement of the user interface object D27 from D27′ to D27″, to D27′″ and finally to D27′ which is proximate to the destination object “Printer” 6042 in FIG. 6J). In some embodiments, as the device moves the first user interface object, the device resizes the user interface object so as to match the size of the destination object. An illustrative example of the movement and resizing (e.g., from D27′, to D27″, D27′, and finally to D27″″ in FIG. 6J) of the destination object is shown in FIG. 63. In this example, the destination object (e.g., “Printer” 6042 in FIG. 63) is larger along the horizontal dimension (i.e., longer) and smaller along the vertical dimension (i.e., shorter) than the first user interface object (e.g., D27′ in FIG. 63). Thus, as illustrated in FIG. 63, the user interface object D27 is stretched horizontally and compressed vertically as it moves (e.g., from D27′, to D27″, to D27′″ and finally to D27″″ in FIG. 6J) towards the destination object 6042. It should be understood that, typically the various resized representations of the user interface object (e.g., D27′, D27″, D27′″ and D27″″ in FIG. 6J) are not simultaneously displayed, but are, instead, displayed in sequence as the user interface object moves along a path towards the destination object. In some embodiments, where the user interface object includes an image, the image is distorted as the object is resized.

In some embodiments, the device detects (1126) lift off of the first input by the user (e.g., lift off of the first finger contact by the user, lift off of the stylus contact, or a mouse up event) from the touch screen display at the destination object or at the area associated with the destination object. In response to detecting lift off of the first input (e.g., contact 6052-5 in FIG. 63) by the user from the touch screen display at the destination object or at the area associated with the destination object, the device performs an action on the first user interface object and the second user interface object (e.g., the device initiates printing of user interface objects D27 and D28). The action is associated with the destination object (e.g., “Print” 6042 in FIG. 63). Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document.

As an example of movement of the first input to an area associated with a destination object, in FIG. 6K, the destination object is the “School garden” icon 6008 and the area associated with the “School garden” icon 6008 is a rectangular area 6076 that includes an array 6072 of images labeled as being images of the “School garden” event. In this example, the first input by the user (e.g., contact 6052) is moved (e.g., movement 6074 in FIG. 6K) to a location 6052-6 within the area 6076 that is associated with the destination object “School garden” icon 6008. While the device is detecting the contact (e.g., 6052-6 in FIG. 6K) in the area 6076 that is associated with the destination object 6008, the device detects lift off of the first input 6052 by the user, as shown in FIGS. 6K-6L (where contact 6052-6 ceases to be detected in FIG. 6L). In response to detecting the lift off of the user input (e.g., the release of contact 6052-6), the device performs an action on the user interface objects (e.g., D27 and D28) that were associated with the first input by the user (e.g., contact 6052). The action is associated with the destination object 6008. In this example, the device associates images D27 and D28 with the “School garden” event 6008 and displays an animation of representations of the user interface objects (e.g., D27′ and D28′ in FIG. 6L) moving into the array 6072 of images labeled as being images of the “School garden” event. In some embodiments, the user interface objects are associated with the new array 6072 in addition to being associated with the old array 6078 of user interface objects to which the user interface objects previously belonged. In contrast, in other embodiments, as shown in FIG. 6M, the user interface objects (e.g., D27 and D28) are associated with the new array (e.g., “School garden” array 6072) and disassociated with the old array to which they previously belonged (e.g., “Day at the zoo” array 6078). In FIG. 6M, the user interface objects D27 and D28 are shown in the new array 6072 of user interface objects, while they are not shown in the old array 6078 of user interface objects, and the remaining user interface objects (e.g., D1-D26 and D29-D36) in the old array 6078 of user interface objects are rearranged to fill in the gaps caused by the removal of the user interface objects D27 and D28.

FIGS. 12A-12B are flow diagrams illustrating a method 1200 of forming a group of user interface objects, moving the group to a destination object or an area associated with a destination object, and performing an action associated with the destination object on the group of user interface objects in accordance with some embodiments. The method 1200 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 6M-6X). Some operations in method 1200 may be combined and/or the order of some operations may be changed.

As described below, the method 1200 provides an intuitive way to form a group of multiple user interface objects and manipulate the group of user interface objects at a computing device with a touch screen display. The method reduces the cognitive burden on a user when manipulating multiple user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate multiple user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1202 on the touch screen display (e.g., 112 in FIG. 6M) a plurality of user interface objects (e.g., digital images D1-D25, D28-D36, and/or S1-S39, D26, D27 in FIG. 6M) and at least one destination object (e.g., icons 6004, 6006, 6008, 6010, 6012, 6014, 6016, 6018, 6020, 6022, 6024, 6028, 6030, 6032, 6034, 6038, 6040, 6042, 6044, 6046, 6048, or 6050). In some embodiments, the user interface objects are ‘selectable objects’ (i.e., objects configured to be selectable by a user).

The device detects (1204) a first input by a user (e.g., a press and hold finger contact 6100, stylus contact, or mouse click) on a first user interface object (e.g., D31 in FIG. 6N) at a first location on the touch screen display.

Operations 1208-1226 are performed while the device continues (1206) to detect the first input (e.g., press and hold finger contact 6100 in FIGS. 6N-6T) by the user.

The device detects (1208) movement (e.g., 6102 in FIG. 6N) of the first input (e.g., 6100-1 in FIG. 6N) by the user across the touch screen display to a second location (e.g., 6100-2 in FIG. 6N) on the touch screen display.

The device moves (1210) the first user interface object in accordance with the movement (e.g., 6102 in FIG. 6N) of the first input by the user across the touch screen display to (or proximate to) the second location (e.g., 6100-2 in FIG. 6N) on the touch screen display. For example, in FIG. 6N the user interface object D31 moves to a location D31′ that is proximate to the second location of the contact (e.g., 6100-2 in FIG. 6N).

The device detects (1212) a second input by the user or series of inputs by the user on two or more user interface objects in the plurality of user interface objects (e.g., a swipe gesture with a finger or stylus that contacts the two or more user interface objects), multiple simultaneous finger gestures (such as concurrent finger contacts on the two or more user interface objects), or a series of tap gestures with a finger or stylus or a series of mouse clicks on the two or more user interface objects). The two or more user interface objects are displayed at respective initial user interface object positions on the touch screen display. If both inputs are finger inputs, the finger that makes the first input by the user is different from the finger that makes the second input by the user or series of inputs by the user. For example, in FIG. 6O, the device detects a finger swipe gesture (e.g., contact 6104 followed by movement 6106 of the contact along the touch-sensitive surface in FIG. 6O), which passes through two or more of the user interface objects (e.g., D36, D33, D30. D25, D22, D19, D16. D13 and D10 in FIG. 6O).

In response to detecting the second input (e.g., swipe gesture including contact 6106-1 and movement 6106 of the contact along the touch-sensitive surface in FIG. 6O) by the user or series of inputs by the user on two or mom user interface objects in the plurality of user interface objects, the device displays (1214) animations of each respective user interface object in the two or more user interface objects moving from a respective initial user interface object position to (or proximate to) the second location. The animations indicate to a user that these user interface objects are being added to the group of user interface objects. The animations may move the two or more user interface objects to, proximate to, or into the first user interface object. For example, as shown in FIG. 6P, as the contact moves 6106 to a second contact location 6104-2 as part of the swipe gesture, respective representations of the user interface objects (e.g., D36′, D33′, D30′, D25′, D22′. D19′, D16′, D13′, and D10′ in FIG. 6P) move towards the second location (e.g., 6100-2 in FIG. 6P), which includes the first user interface object (e.g., D31′ in FIG. 6P).

In some embodiments, the device displays (1216) a counter (e.g., 6108-a in FIG. 6Q) of the number of user interface objects that have moved to the second location (e.g., in response to detecting the second input by the user or series of inputs by the user on the two or more user interface objects). In the example above, as the device is animating the movement of the second user interface objects to the first user interface object, the device displays a counter showing “10” (e.g., 6108-a in FIG. 6Q) to indicate that ten user interface objects (e.g., D10, D13, D16, D19, D22, D25, D30, D31, D33 and D36) have moved to the second location.

In some embodiments, in response to detecting the second input by the user or series of inputs by the user on the two or more user interface objects, the device displays (1218) a residual image (e.g., the shaded user interface objects D10, D13, D16, D19, D22, D25, D30, D31, D33 and D36 in FIG. 6P-6Q) for each of the two or more user interface objects at a respective initial user interface object position on the touch screen display.

In some embodiments, the device detects (1220) a third input by the user (e.g., a finger gesture such as a tap gesture 6110 in FIG. 6Q, a stylus tap gesture, or a mouse input such as a mouse click when a cursor controlled by the mouse is over a respective residual image of a respective user interface object) on a respective residual image (e.g., shaded user interface object D25 in FIG. 6Q) of a respective user interface object at a respective initial user interface object position on the touch screen display while continuing to detect the first input (e.g., contact 6100-2 in FIG. 6Q) by the user. In response to detecting the third input (e.g., tap gesture 6110 in FIG. 6Q) by the user on the respective residual image of the respective user interface object at the respective initial user interface object position on the touch screen display, the device displays the respective user interface object at the respective initial user interface object position (e.g., unshaded user interface object D25 in FIG. 6S).

In some embodiments, the device displays (1222) an animation of the respective user interface object moving from the second location back to the respective initial user interface object position. The animation indicates to a user that the respective user interface object is being removed from the group of objects at the second location. The animation may move the respective user interface object from or out of the first user interface object. For example, in FIG. 6R, a representation of the second user interface object (e.g., D25′) is shown moving from the first user interface object (e.g., D31′ in FIG. 6R) towards the initial position of the second user interface object (e.g., D25 in FIG. 6R). In some embodiments, the device displays a counter (e.g., 6108-b in FIG. 6R) of the number of user interface objects that are still located at the second location. In the example above, as the device is animating the movement (e.g., 6112 in FIG. 6R) of the second user interface object to the initial second user interface object position on the touch screen, the device decrements a counter to “9” (e.g., 6108-b in FIG. 6R) to indicate that only nine of the user interface objects (e.g., D10, D13, D16, D19, D22, D30, D31, D33 and D36) remain in the second location. It should be understood that only nine user interface objects “remain” at a location because ten user interface objects (e.g., D10, D13, D16, D19, D22, D25, D30, D31, D33 and D36) have moved to the location and one (e.g., D25) has moved away from the location.

In some embodiments, the device detects (1224) movement of the first input (e.g., movement 6114 in FIG. 6S, which includes movement of contact 6100 from contact location 6100-2 to contact location 6100-3, to contact location 6100-4, to contact location 6100-5) by the user across the touch screen display from the second location (e.g., 6100-2) to a destination object (e.g., “School garden” event icon 6008 in FIG. 6S) or an area associated with a destination object. The device moves the first user interface object (and, in some embodiments, the two or more user interface objects) in accordance with the movement of the first input by the user across the touch screen display to the destination object or the area associated with a destination object (e.g., movement of the user interface object D31 from D31′ to D31″, to D31′″ and finally to D31″″ which is proximate to the destination object “School garden” 6008 in the menu in FIG. 6S). In some embodiments, as the device moves the first user interface object, the device resizes the user interface object so as to match the size of the destination object. An illustrative example of the movement and resizing (e.g., from D31′, to D31″, D31′″, and finally to D31″″ in FIG. 6S) of the destination object is shown in FIG. 5S. In this example, the destination object is larger along the horizontal dimension (i.e., longer) and smaller along the vertical dimension (i.e., shorter) than the first user interface object. Thus, as illustrated in FIG. 6S, the user interface object D31 is stretched horizontally and compressed vertically as it moves (e.g., from D31′, to D31″, to D31′″ and finally to D31″″ in FIG. 6S) towards the destination object 6008 in FIG. 6J. It should be understood that, typically the various resized representations of the user interface object (e.g., D31′, D31″, D31′″ and D31′″ in FIG. 6S) are not simultaneously displayed, but are instead displayed in sequence as the user interface object moves along a path towards the destination object. In some embodiments, where the user interface object includes an image, the image is distorted as the object is resized.

In some embodiments, the device detects (1226) lift off of the first input by the user (e.g., lift off of the first finger contact by the user, lift off of the stylus contact, or a mouse up event) from the touch screen display at the destination object or at the area associated with the destination object. In response to detecting lift off of the first input (e.g., lift off of contact 6100-5 in FIG. 6S) by the user from the touch screen display at the destination object or at the area associated with the destination object, the device performs an action on the first user interface object and the two or more user interface objects (e.g., the device associates images D10, D13, D16, D19, D22. D30, D31, D33 and D36 with the “School garden” event that is associated with destination object 6008, as shown in FIG. 6X). The action is associated with the destination object (e.g., “School garden” event icon 6008 in FIG. 6S). Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document.

As an example of movement of the first input to an area associated with a destination object, in FIG. 6T, the destination object is the “School garden” icon 6008 and the area associated with the “School garden” icon 6008 is a rectangular area 6076 that includes an array 6072 of images labeled as being images of the “School garden” event. In this example, the first input by the user (e.g., contact 6100) is moved (e.g., movement 6116 in FIG. 6T) to a location 6100-6 within the area 6076 that is associated with the destination object “School garden” icon 6008. While the device is detecting the contact (e.g., 6100-6 in FIG. 6T) in the area 6076 that is associated with the destination object 6008, the device detects lift off of the first input 6100 by the user, as shown in FIG. 6U. In response to detecting the lift off of the user input (e.g., the release of contact 6100-6 in FIG. 6U), the device performs an action on the user interface objects (e.g., D10, D13. D16, D19, D22, D30, D31, D33 and D36) that were associated with the first input by the user (e.g., contact 6100). The action is associated with the destination object 6008. In this example, the device associates images D10, D13, D16, D19, D22, D130, 31, D33 and D36 with the “School garden” event 6008 and displays an animation of representations of the user interface objects (e.g., D10′, D13′, D16′, D19′, D22′, D30′, D31′, D33′ and D36′ in FIGS. 6V and 6W) moving into the array 6072 of images labeled as being images of the “School garden” even. In some embodiments, the user interface objects are associated with the new array 6072 in addition to being associated with the old array 6078 of user interface objects to which the user interface objects previously belonged. In contrast, in other embodiments (e.g., as shown in FIG. 6X), the user interface objects (e.g., D10, D13, D16, D19, D22, D30, D31, D33 and 36) are associated with the new array (e.g., “School garden” array 6072) and disassociated with the old array to which they previously belonged (e.g., “Day at the zoo” array 6078). In FIG. 6X, the user interface objects D10, D13, D16, D19, D22, D30, D31, D33 and D36 are shown in the new array 6072 of user interface objects, while they are not shown in the old array 6078 of user interface objects, and the remaining user interface objects (e.g., D1-D9, D11-D12, D14-D15, D17-D18, D20-D21, D23-D25, D26, D29, D32 and D34-D35) in the old array 6078 of user interface objects are rearranged to fill in the gaps caused by the removal of the user interface objects D10, D13, D16, D9, D22, D30, D31, D33 and 36.

FIGS. 13A-13B are flow diagrams illustrating a method 1300 of zooming and rearranging user interface objects in an array with a multifinger gesture in accordance with some embodiments. The method 1300 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 7A-7O). Some operations in method 1300 may be combined and/or the order of some operations may be changed.

As described below, the method 1300 provides a way to keep track of a particular user interface object in an array when the array is rearranged after enlargement of the particular user interface object (and, typically, other user interface objects in the array) in response to a multitouch gesture. The method reduces the cognitive burden on a user of finding the particular user interface object after rearrangement of the array by keeping the particular user interface object at the same (or substantially the same) vertical position on the touch screen display just before and just after the rearrangement of the array, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to faster and more efficiently locate a user interface object in an array conserves power and increases the time between battery charges.

The device simultaneously displays (1302) on the touch screen display (e.g., 112 in FIG. 7A) a plurality of user interface objects (e.g., digital images S1-S41 in FIG. 7A) in an array 7002 (e.g., an array of digital images for an event labeled “School garden” FIG. 7A). The plurality of user interface objects in the array are displayed in a first arrangement 7002-1 (e.g., an array with three rows, with images in increasing number/time going from left to right across each row, from top to bottom in the array, as shown in FIG. 7A, where S1 has an earlier time than S2 and S2 has an earlier time than S3, and so on). A first user interface object (e.g., image S23) in the plurality of user interface objects is displayed at a first size (e.g., one half inch tall). The first arrangement comprises a first plurality of rows (e.g., three rows, S1-S18, S19-S34 and S35-S41).

The device detects (1304) simultaneous contacts (e.g., 7004 and 7006 in FIG. 7B) by a plurality of fingers (e.g., two fingers) on the array 7002. The simultaneous contacts have a corresponding centroid (e.g., 7008, FIG. 7B) position at the first user interface object. For example, when simultaneous contacts 7004-1 and 7006-1 are initially made on the touch screen display, the position of the centroid 7008-1 of the simultaneous contacts is located within the first user interface object S23.

The device detects (1306) a gesture (e.g., a depinch gesture) made by the simultaneous contacts that corresponds to a command to zoom in by a user-specified amount. For example, in FIG. 7C, the simultaneous contacts include a first contact 7004-1 and a second contact 7006-1 and the device detects a depinch gesture (e.g., a gesture where the simultaneous contacts move apart from each other on the touch sensitive surface). In this example, the device detects movement 7010 of the first contact 7004-1 to a new position of the first contact (e.g., contact 7004-2 in FIG. 7D. The device also detects movement 7012 of the second contact 7006-1 to a new position of the second contact (e.g., contact 7006-2 in FIG. 7D.

In response to detecting the gesture (e.g., the depinching gesture) by the simultaneous contacts, the device enlarges (1308) the first user interface object (e.g., S23 in FIG. 7D to a second size larger than the first size on the touch screen display (e.g., one inch tall). In some embodiments, in response to detecting the gesture by the simultaneous contacts, the device enlarges (1310) other user interface objects (e.g., S4-S11, S21-S22, S24-S28, S38-S41, etc. in FIG. 7D in the array at the same time as the first user interface object and by the same amount as the first user interface object. In other words, if the first interface object S23 is one half inch tall before the gesture is detected and one inch tall after the gesture is detected, then if the other user interface objects in FIG. 7C are one half inch tall before the gesture is detected, they will also be one inch tall after the gesture has been detected, as illustrated in FIG. 7D. In some embodiments, respective user interface objects in the array maintain (1312) their respective positions in the array during the enlarging. For example, in FIG. 7D, respective images in the array 7002-1 with three Tows maintain their respective positions in the array during the enlarging, even though not all of the images are displayed on the touch screen display after the enlarging.

After enlarging the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, the device determines (1314) an updated centroid position (e.g., 7008-2 in FIG. 7D) of the simultaneous contacts. The updated centroid position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. As shown in FIG. 7D, the vertical position of the updated centroid 7008-2 is higher on the display than the initial vertical position of the centroid 7008-1. In this case, the vertical movement (e.g., 7014 in FIG. 7D) of the centroid from its initial position 7008-1 to its updated position 7008-2 is due to an uneven depinch gesture, where one of the contacts (e.g., contact 7004) moved further from the initial centroid position than the other contact (e.g., contact 7002) during the depinch gesture. However, it should be understood that both of the contacts (e.g., 7002 and 7004) could move simultaneously either up or down on the display (e.g., as illustrated in FIGS. 7J-7K), which would also result in vertical movement of the updated centroid position.

The device ceases (1316) to detect the simultaneous contacts (e.g., detecting lift off of all of the simultaneous contacts 7004-2 and 7006-2 in FIG. 7D, as shown in FIG. 7E).

In response to ceasing to detect the simultaneous contacts, the device displays (1318) an animation of the plurality of user interface objects in the array rearranging to form a second arrangement. The second arrangement typically conforms the layout of the enlarged user interface objects to a predefined area of the display (such as the area where a plurality of arrays are being displayed). The second arrangement comprises a second plurality of rows different from the first plurality of rows. The first user interface object is displayed in a row in the second arrangement that includes (e.g., overlaps) the first vertical position on the touch screen display.

For example, in FIG. 7F the user interface objects are shown rearranging to form a second arrangement. In this example, the user interface objects have divided into groups of user interface objects (e.g., S2-S7, S8-S12, S19-S20, S21-S27, S28-S30 and S36-S41). In this example, there are fewer groups of user interface objects than there are user interface objects (e.g., in some embodiments, the user interface objects do not move independently, but rather move in groups). For this example, within each group of user interface objects, the user interface objects do not move relative to each other. For example, the horizontal neighbors to S23 (e.g., S22 and S24 in FIG. 7E) remain the horizontal neighbors of S23 in FIGS. 7F and 7O while the animation is being displayed, and continue to be the neighbors of S23 in the second arrangement, as shown in FIG. 7H. In contrast the vertical neighbors of S23 (e.g., S6, S40 and S41 in FIG. 7E) in this example cease to be neighbors of S23, because they are not part of the same group as S23. In this example, each of these groups of user interface objects moves independently to a location in the second arrangement. FIG. 7G illustrates a continuation of the exemplary animation as the groups of user interface objects rearrange to form the second arrangement of the array 7002-2 (FIG. 7H).

As noted above, the second arrangement comprises a second plurality of rows different from the first plurality of rows. For example, in array 7002-2 in FIG. 7H, there are six rows: S1-S7, S8-S13, S14-S20, S21-S27, S28-S34 and S35-S41, as opposed to the three rows in array 7002-1 that were displayed by the device before rearranging the user interface objects, as illustrated in FIG. 7A.

As noted above, the first user interface object S23 is displayed in a row in the second arrangement that includes (e.g., overlaps) the first vertical position (e.g., the vertical position of the updated centroid 7008-2 in FIGS. 7D-7H) on the touch screen display. In some embodiments, the user interface objects in the second arrangement are arranged according to the same criteria as the user interface objects in the first arrangement (e.g., in increasing number/time going from left to right across each row, from top to bottom in the array, as shown in FIG. 7H, where S1 has an earlier time than S2 and S2 has an earlier time than S3, and so on), while taking into account the change in size of the objects and the resulting change in the number of rows.

The first user interface object has a vertical position on the touch screen display. In some embodiments, the vertical position of the first user interface object moves (1320) in accordance with detected vertical movement of the centroid of the simultaneous contacts prior to ceasing to detect the simultaneous contacts. For example, in FIG. 7D the centroid position of the simultaneous contacts is shown as having moved a vertical distance 7014 from the initial centroid position. In this example, as shown in FIG. 7D, the vertical position of the first user interface object S23 moves by an amount that corresponds to the vertical movement 7014 of the centroid of the simultaneous contacts.

In some embodiments, the plurality of user interface objects are (1322) displayed at the second size in the second arrangement. For example, in FIG. 7H, the user interface objects (e.g., S1-S41) are shown as being one inch high in the second arrangement (e.g., the arrangement in FIG. 7H with six rows of user interface objects).

In some embodiments, an analogous rearrangement process occurs after the device detects a gesture made by the simultaneous contacts that corresponds to a command to zoom out by a user-specified amount (e.g., a two-finger pinch gesture) and then the device ceases to detect the simultaneous contacts.

An illustrative example of the analogous rearrangement process is described below with reference to FIGS. 7I-7O. The device detects simultaneous contacts (e.g., 7016 and 7018 in FIG. 7I) by a plurality of fingers (e.g., two fingers) on the array 7002-2. The simultaneous contacts have a corresponding centroid (e.g., 7020 in FIG. 7I) position at a first user interface object. For example, when the simultaneous contacts 7016-1 and 7018-1 are initially made on the touch screen display, the position of the centroid 7020-1 of the simultaneous contacts is located within the first user interface object S9.

Continuing this example, in FIG. 7I, the simultaneous contacts include a first contact 7016-1 and a second contact 7018-1 and the device detects a pinch gesture (e.g., a gesture where the simultaneous contacts move towards each other on the touch sensitive surface). In this example, the device detects movement 7022 of the first contact 7016-1 to a new position of the first contact (e.g., 7016-2 in FIG. 7I) and movement 7024 of the second contact 7018-1 to a new position of the second contact (e.g., 7018-2 in FIG. 7J). In response to detecting the pinching gesture, the device reduces the size of the first user interface object (e.g., S9 in FIG. 7J) to a new size (e.g., three quarters of an inch tall) smaller than the previous size (e.g., one inch tall) on the touch screen display. In some embodiments, in response to detecting the gesture by the simultaneous contacts, the device reduces the size of other user interface objects (e.g., S4-S11, S21-S22, S24-S28, S38-S41, etc. in FIG. 7J) in the array at the same time as the first user interface object (e.g., S9 in FIG. 7J) and by the same amount as the first user interface object. In other words, if the first interface object S9 is one inch tall before the gesture is detected and three quarters of an inch tall after the gesture is detected, then if the other user interface objects in FIG. 7I are one inch tall, they will be three quarters of an inch tall after the gesture has been detected, as illustrated in FIG. 7W. In some embodiments, respective user interface objects in the array maintain their respective positions in the array during the reducing. For example, in FIG. 7I, there are still six rows of images that are arranged in ascending order left to right, top to bottom, and each of the images is still next to the same images that it was next to before the images were reduced in size (e.g., in FIG. 7I).

In some embodiments, after detecting the pinching gesture, the device detects additional movement of the contacts. In the present example, this additional movement is a vertical translation of the contacts (e.g., 7016-2 and 7018-2 in FIG. 7J) down the touch screen, including movement (e.g., movements 7026 and 7028, respectively in FIG. 7J) of the contacts downwards to new positions (e.g., 7016-3 and 7018-3 in FIG. 7K) on the touch screen display. As the contacts move downwards, the current centroid (e.g., 7020-1 in FIG. 7J) position of the contacts also moves downwards (7030 in FIG. 7K) to a new position (e.g., 7020-2 in FIG. 7K), as does the entire array 7002.

In the present example, after reducing the size of the first user interface object to the second size and while continuing to detect the simultaneous contacts on the touch screen display, the device determines the updated centroid (e.g., 7020-2 in FIG. 7K) position of the simultaneous contacts. The updated centroid (e.g., 7020-2 in FIG. 7K) position is located at a first vertical position on the touch screen display immediately prior to ceasing to detect the simultaneous contacts. As shown in FIG. 7K, the vertical position of the updated centroid 7020-2 is lower on the display than the initial vertical position of the centroid 7020-1. In this case, the vertical movement (e.g., 7030 in FIG. 7K) of the centroid from its initial position 7020-1 to its updated position 7020-2 is due to a movement of the simultaneous contacts (e.g., 7016 and 7018) after the pinch gesture was detected. But it should be understood that the position of the centroid may change at any time due to the movement of one or more of the simultaneous contacts.

Continuing this example, the device ceases to detect the simultaneous contacts (e.g., detecting lift off of all of the simultaneous contacts, as shown in FIG. 7X). In response to ceasing to detect the simultaneous contacts, the device displays an animation of the plurality of user interface objects in the array rearranging to form a third arrangement. The third arrangement typically conforms the layout of the reduced user interface objects to a predefined area of the display (such as the area where a plurality of arrays are being displayed). For example, in FIGS. 7M-7O the user interface objects are shown rearranging to form a third arrangement of the array 7002-3. In this example, the user interface objects have divided into groups of user interface objects (e.g., S1-S7, S8-S12, S13, S14-S20, S21-S24, S25-S27, S28-S34, S35-S36 and S37-41). It should be noted that these groups of user interface objects are different from the groups of user interface objects formed in the previous example. In this example, within each group of user interface objects, the user interface objects do not move relative to each other. For example, the horizontal neighbors to S9 (e.g., S8 and S10 in FIG. 7L) remain neighbors of S9 in FIGS. 7M and 7N while the animation is being displayed, and continue to be the neighbors of S9 in the second arrangement as shown in FIG. 7O. In contrast the vertical neighbors of S9 (e.g., S3, S15 and S16 in FIG. 7L) in this example cease to be neighbors of S9 while the animation is displayed, because they are not part of the same group as S9. In this example, each of these groups of user interface objects moves independently to a location in the third arrangement. FIG. 7N illustrates a continuation of the exemplary animation as the groups of user interface objects rearrange to form the third arrangement. FIG. 7O illustrates the third arrangement of the array 7002-3.

It should be noted that in the third arrangement (e.g., the arrangement in FIG. 7O with four rows: S1-S12, S13-S24, S25-S36, S37-S41), the user interface object (e.g., S9) that was proximate to the updated centroid position 7020-2 when the simultaneous contacts were released (e.g., as shown in FIG. 7L) is at the same vertical position as the updated centroid position 7020-2, even though it is not at the same horizontal position. Typically, if the user is attempting to manipulate a particular user interface object, that object will be proximate to the centroid of any multitouch gesture performed by the user to resize the array. By positioning the user interface object that was proximate to the updated centroid position at the same vertical position as the updated centroid position immediately prior to lift off of the simultaneous contacts, the user interface object that the user was manipulating remains at the same (or nearly the same) vertical position on the touch screen display. Thus, the user is able to more easily locate this user interface object after rearrangement of the array.

FIGS. 14A-14I are flow diagrams illustrating a method 1400 of manipulating user interface objects in a plurality of arrays of user interface objects in accordance with some embodiments. The method 1400 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 8A-8UU). Some operations in method 1400 may be combined and/or the order of some operations may be changed.

As described below, the method 1400 provides an intuitive way to manipulate user interface objects in large data sets at a computing device with a touch screen display. The method reduces the cognitive burden on a user when performing actions on user interface objects in large data sets, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate user interface objects in a plurality of arrays faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1402) on the touch screen display (e.g., 112 in FIG. 8A) at least one destination object (e.g., an array name icon in a list or menu of such icons, such as one or more of array name icons 8004, 8006, 8008, 8010, 8012, 8014, 8016, 8018, 8020, 8022, 8024, 8028, 8030, 8032, 8034, 8038, 8040, 8042, 8044, 8046, 8048, and/or 8050) and at least a subset of a plurality of arrays of user interface objects. For example, as shown in FIG. 8A, there are two arrays of user interface objects, a “Day at the zoo” array 8052 that includes a plurality of user interface objects (e.g., digital images D1-D36) from an event labeled “Day at the zoo” and a “School garden” array 8054 that includes a plurality of user interface objects (e.g., S1-S41). Depending on the number of arrays, it may not be possible to simultaneously display every array in the plurality of arrays. In such cases, a subset of the plurality of arrays is displayed and different subsets may be viewed by scrolling the plurality of arrays (e.g., in response to detecting a first finger swipe gesture on the touch screen display, such as a vertical or substantially vertical finger swipe gesture, as described in greater detail below with reference to FIGS. 8B-8D.

In some embodiments, the device displays (1404) a respective representative user interface object (e.g., digital image S33-r, which is representative of the digital images in array 8054 in FIG. 8A) adjacent to a respective array (e.g., the “School garden” array 8054 in FIG. 8A) for at least some arrays in the plurality of arrays.

In some embodiments, the device displays (1406) a respective representative user interface object toggle icon (e.g., icon 8056 in FIG. 8A) for a respective array (e.g., 8054 in FIG. 8A) in the plurality of arrays. The representative user interface object toggle icon is operable to toggle display of the respective representative user interface object (e.g., image S33-r in FIG. 8A) on and off. In some embodiments, each array in the plurality of arrays has (1408) a corresponding representative user interface object toggle icon.

In some embodiments, the representative user interface object toggle icon (e.g., S33-r in FIG. 8A) is (1410) displayed adjacent to a respective representative user interface object when the respective representative user interface object is displayed and the representative user interface object toggle icon (e.g., 8056 in FIG. 8A) is displayed adjacent to a respective array (e.g., 8054 in FIG. 8Q) when the respective representative user interface object is not displayed, as illustrated in FIG. 8Q, which is described in more detail below. In some embodiments, the device displays (1412) a respective array name icon (e.g., “School garden” 8058 in FIG. 8A) adjacent to the respective representative user interface object toggle icon (e.g., 8056 in FIG. 8A).

The device detects (1414) a first input by a user (e.g., a vertical or substantially vertical finger swipe gesture or stylus swipe gesture) on the touch screen display. For example, in FIG. 8B, the device detects a vertical swipe gesture that includes a contact 8060-1 with the touch screen display and subsequent movement 8062 of the contact along the touch screen display to a new location (e.g., contact 8060-2 in FIG. 8C). In some embodiments, the first input by the user may be detected anywhere on the touch screen display. In some embodiments, the first input by the user must be detected in a predefined area on the touch screen display, such as the area that displays the plurality of arrays (as shown in FIG. 8B).

In response to detecting the first input by the user on the touch screen display, the device vertically scrolls (1416) the plurality of arrays on the touch screen display. For example, in FIG. 8B, the currently displayed arrays are “Day at the zoo” 8052 and “School garden” 8054. After detecting the first input by the user (e.g., swipe gesture including contact 8060-1 and movement 8062 of the contact in FIG. 8B), the device scrolls through the arrays so that new arrays (e.g., the “Family reunion” array 8064 and the “Southern Europe” array 8066 in FIG. 8C) are displayed in the display region. In this example, the newly displayed arrays each include a plurality of user interface objects: the “Family reunion” array 8064 includes 17 user interface objects” (e.g., F1-F17), all of which are displayed; and the “Southern Europe” array 8066 includes 74 user interface objects, only some of which (e.g., E1-E54) can be displayed, while other user interface objects in the array (e.g., E55-E74) are not displayed, but can be revealed by the device in response to gestures from the user.

In some embodiments the device continues to scroll (e.g., as illustrated by arrow 8068 in FIG. 8C) the display of the device for a predetermined period of time after the device detects the end of the first user input (e.g., the end of the movement of the contact along the touch sensitive-surface during the swipe gesture). In some embodiments, this movement after detecting an end of the first user input gradually slows down, creating an inertia-like effect, as though the arrays were sliding along a physical surface and gradually slow down due to friction.

The device detects (1418) a second input by the user (e.g., a horizontal or substantially horizontal finger swipe gesture or stylus swipe gesture) on a single array in the plurality of arrays on the touch screen display. For example, in FIG. 8D, the second input is a horizontal swipe gesture that includes a contact 8070-1 with an array 8066 and subsequent movement 8072 of the contact to a new location (e.g., 8070-2 in FIG. 8E).

In response to detecting the second input by the user on the single array, the device horizontally scrolls (1420) user interface objects in the single array without horizontally scrolling other arrays in the plurality of arrays. In the example above, user interface objects in the array (e.g., 8066 in FIG. 8D are scrolled horizontally (e.g., to the left) so that some of the previously displayed user interface objects are hidden (e.g., in FIG. 8D, before the scrolling of the user interface objects, user interface objects E1-E24 are displayed, while in FIG. 8E, after the scrolling of the user interface objects, user interface objects E1-E24 are no longer displayed.) Similarly, in the example above, some of the user interface objects that were previously hidden are displayed as a result of the horizontal scrolling (e.g., in FIG. 8D, before the scrolling of the user interface objects, user interface objects E55-E74 are not displayed, while in FIG. 8E, after the scrolling of the user interface objects, user interface objects E55-E74 are displayed.)

In some embodiments, the device displays a rubber-band-like effect to indicate that either the beginning or the end of an array is being displayed during detection of a horizontal scrolling gesture. To indicate the end of an array is being displayed, there is an invisible vertical edge 8074 at the right side of the display (FIG. 8E). The user interface objects in an array (e.g., array 8066, FIG. 8E) are horizontally scrolled (e.g., as shown by the leftward pointing arrow 8076 in FIG. 8E) beyond that edge during detection of a horizontal scrolling gesture (e.g., by contact 8070). After detecting lift off of the contact (e.g., lift off of 8070-2 in FIG. 8E), the device horizontally scrolls (e.g., as shown by the rightward pointing arrow 8078 in FIG. 8E) the user interface objects in the array 8066 back towards the edge 8074 so that the right edge of the rightmost user interface objects at the end of the array (e.g., images E73 and E74 in FIG. 8F) are proximate to the edge 8074. A rubber-band-like effect that is used to indicate that the beginning an array is being displayed during detection of a horizontal scrolling gesture is described in operation 1421 below.

As a further example of the device scrolling a single array of user interface objects horizontally, the device may also detect a horizontal swipe gesture including a contact (e.g., 8080-1 in FIG. 8G) with an array (e.g., 8066 in FIG. 8G) and subsequent movement (e.g., 8082 in FIG. 8G) of the contact to a new location (e.g., 8080-2 in FIG. 8H). In this example, after detecting the horizontal swipe gesture on the array (e.g., 8066 in FIG. 8G), the device horizontally scrolls user interface objects in the single array to the right without horizontally scrolling other arrays in the plurality of arrays. In this example, user interface objects in the array (e.g., 8066 in FIG. 8G) are scrolled horizontally (e.g., to the right) so that some of the previously displayed user interface objects are hidden (e.g., in FIG. 8G, before the scrolling of the user interface objects, user interface objects E55-E74 are displayed, while in FIG. 8H, after the scrolling of the user interface objects, user interface objects E55-E74 are no longer displayed.) Similarly, in this example, some of the user interface objects that were previously hidden are displayed as a result of the horizontal scrolling (e.g., in FIG. 8G, before the scrolling of the user interface objects, user interface objects E1-E24 are not displayed, while in FIG. 8H, after the scrolling of the user interface objects, user interface objects E1-E24 are displayed.)

In some embodiments, the device displays (1421) respective representative user interface objects for respective arrays (e.g., representative images F8-r and E45-r in FIG. 8G). The respective representative user interface objects are aligned to a common vertical edge on the touch screen display. For example, in FIG. 8G, the edges of the representative user interface objects (e.g., representative images F8-r and E45-r in FIG. 8G) are aligned with vertical edge 8084. The device displays a first portion of the single array adjacent to a representative user interface object for the single array (e.g., images E25-E74 in FIG. 8G). The device detects an input by the user (e.g., a finger contact 8080-1 or stylus contact) on the single array. The device detects a movement (e.g., movement 8082 in FIG. 8G) of the input by the user on the touch screen display. In response to detecting the movement, the device horizontally scrolls (e.g., as shown in FIGS. 8G-8H) the single array (e.g., 8066 in FIGS. 8G-8H) on the touch screen display in a first direction to display a second portion of the single array (e.g., images E1-E45 in array 8066, as shown in FIG. 8H). The second portion (e.g., images E1-E45 in FIG. 8H) is different from the first portion (e.g., images E25-E74 in FIG. 8G). In response to an edge of the single array being reached while horizontally scrolling the single array in the first direction while the input by the user is still detected on the touch screen display (e.g., contact 8070-2 in FIG. 8H), the device displays horizontal movement (e.g., movement 8086 in FIG. 8H) of the representative user interface object (e.g., image E45-r in FIG. 8H) for the single array (e.g., 8066 in FIG. 8H) in the first direction and the device displays horizontal movement of the single array in the first direction, (e.g., user interface objects E25-E74 move to the right from FIG. 8G to FIG. 8H). In some embodiments, the edge of the single array corresponds to an edge of a first user interface object (e.g., E1, E2 or E3 in FIG. 8H) in the single array (e.g., 8066 in FIG. 8H), such as a leftmost user interface object in the single array. In response to detecting lift off of the input (e.g., contact 8070-2 in FIG. 8H) by the user (e.g., lift off of the finger contact or stylus contact) from the touch screen display, the device displays horizontal movement (e.g., movement 8088 in FIG. 8H) of the representative user interface object for the single array (and the single array) in a second direction (e.g., to the left) that is opposite the first direction (e.g. the prior movement 8086 in FIG. 8H of the representative user interface object E45-r and the array to the right) until the representative user interface object for the single array aligns with the common vertical edge (e.g., the left edge of image E45-r aligns with vertical edge 8084).

In some embodiments, the device displays (1422) a list of array name icons (e.g., in FIGS. 8A and 8I, the event list 8002 with event icons 8004, 8006, 8008, 8010, 8012, 8014, 8016, 8018, 8020, 8022 and 8024) that correspond to the plurality of arrays. The list of array names is displayed adjacent to the displayed subset of the plurality of arrays. For example, array name icon “Day at the zoo” 8006 corresponds to the “Day at the zoo” array 8052 shown in FIG. 8A; array name icon “School garden” 8008 corresponds to the “School garden” array 8054 shown in FIG. 8A; array name icon “Family reunion” 8010 corresponds to the “Family reunion” array 8064 shown in FIG. 8I; and the array name icon “Southern Europe” 8066 corresponds to the “Southern Europe” array 8066 shown in FIG. 8I.

In some embodiments, the device detects (1424) a third input by the user (e.g., a finger tap gesture 8090 in FIG. 8I, a stylus tap gesture, or a mouse click when a cursor controlled by the mouse is over the respective array name icon in the list) on a respective array name icon (e.g., “Day at the zoo” 8006 in FIG. 8I) in the list of array name icons. In response to detecting the third input by the user (e.g., tap gesture 8090 in FIG. 8I) on the respective array name icon (e.g., 8006 in FIG. 8I) in the list of array name icons, the device displays an array corresponding to the respective array name icon (e.g., as shown in FIG. 8K, the “Day at the zoo” array 8052 is displayed).

In some embodiments, the device detects (1426) a third input by the user (e.g., a finger tap gesture 8090 in FIG. 8I, a stylus tap gesture, or a mouse click when a cursor controlled by the mouse is over the respective array name icon in the list) on a respective array name icon (e.g., “Day at the zoo” 8006 in FIG. 8I) in the list of array name icons. In response to detecting the third input by the user on the respective array name icon in the list of array name icons, the device scrolls (as shown in FIGS. 81-8K) the plurality of arrays to an array corresponding to the respective array name icon (e.g., “Day at the zoo” array 8052 in FIG. 8K).

For example, in FIG. 8I the device detects a tap gesture 8090 on the “Day at the zoo” icon 8006. The event list 8002 indicates that the “Day at the zoo” array is above the “Family reunion” array 8064, and thus the device begins to scroll the plurality of arrays downwards (e.g., because the “Day at the zoo” array name icon in FIG. 8I is above the “Family reunion” array name icon in FIG. 8I). In response to detecting the tap gesture 8090, the device scrolls (8092, in FIG. 8I) the arrays (e.g., 8064, 8066) towards the bottom of the display. As shown in FIG. 83, the device continues to scroll (8094 in FIG. 83) the arrays towards the bottom of the display (e.g., the “Southern Europe” array 8066 begins to move off of the bottom of the screen) and scrolls newly displayed arrays from the top of the screen (e.g., the “School garden” array 8054 is displayed near the top of the screen in FIG. 83). In this example, the device stops scrolling once the array (e.g., 8052 in FIG. 8K) that is associated with the “Day at the zoo” array name icon (e.g., 8006 in FIG. 8K) is displayed on the display.

In some embodiments, the device detects (1430) a depinching finger gesture (e.g., a two-finger depinching gesture) on a first array in the plurality of arrays. For example, in FIG. 8K, the device detects simultaneous contacts (e.g., 8096-1 and 8098-1 on the “School garden” array 8054 in FIG. 8K) and movement (e.g., 8100 and 8102 in FIG. 8K) of the contacts to a new location (e.g., 8096-2 and 8098-2 in FIG. 8L). In response to detecting the depinching finger gesture on the first array (e.g., 8054 in FIG. 8K) in the plurality of arrays, the device enlarges user interface objects (e.g., S13-S41 in FIG. 8K are enlarged and displayed as S13-S41 in FIG. 8L) in the first array (e.g., 8054 in FIG. 8L) without enlarging user interface objects in arrays other than the first array. For example, the user interface objects (e.g., images D1-D36) in the “Day at the zoo” array in FIG. 8K are the same size as the user interface objects (e.g., images D1-D36) in the “Day at the zoo” array 8052 in FIG. 8L after the zooming operation has been performed. In some embodiments, the user interface objects in the first array are (1432) enlarged up to a predetermined maximum size. In some embodiments, the user interface objects in the first array are (1434) enlarged by the same amount.

In some embodiments, the device displays (1436) a first representative user interface object adjacent to the first array (e.g., representative image S33-r for array 8054 in FIG. 8L). In response to detecting the depinching finger gesture on the first array, the device enlarges the first representative user interface object (e.g., the representative image S33-r is larger in FIG. 8L after the depinching gesture than the representative image S33-r in FIG. 8K before the depinching gesture). In some embodiments, the first representative user interface object and the user interface objects in the first array are (1438) enlarged simultaneously. For example, the device detects simultaneous contacts (e.g., 8096-1 and 8098-1 on the “School garden” array 8054 in FIG. 8K) and movement (e.g., 8100 and 8102 in FIG. 8K) of the contacts to a new location (e.g., 8096-2 and 8098-2 in FIG. 8L). In response to detecting this gesture, the device simultaneously enlarges the representative image S33-r and images S1-S39 in array 8054, as shown in FIGS. 8K-8L.

It should be noted that in the example shown in FIG. 8L, when the user interface objects in the expanded array are expanded, the device is no longer able to display all of the user interface objects in a single view (e.g., in FIG. 8L, user interface objects S1-S12 are not displayed in the first array 8054). In some embodiments, in order to allow the user to access these user interface objects, the device rearranges the user interface icons, as described in greater detail above with reference to FIGS. 7A-7O. In some embodiments, in order to allow the user to accesses these user interface objects the device changes the display of the user interface objects in the array in response to user inputs. For example, in response to a horizontal swipe gesture (e.g., contact 8104 and movement 8106 of the contact substantially horizontal to the direction of the array, as shown in FIG. 8M), the device scrolls the user interface objects in the array of user interface objects. In this example, user interface objects in the array (e.g., 8054 in FIG. 8M) are scrolled horizontally (e.g., to the right) so that some of the previously displayed user interface objects are hidden (e.g., in FIG. 8M, before the scrolling of the user interface objects, user interface objects S31-S41 are displayed, while in FIG. 8N, after the scrolling of the user interface objects, user interface objects S3I-S4l are no longer displayed.) Similarly, in the example above, some of the user interface objects that were previously hidden are displayed as a result of the horizontal scrolling (e.g., in FIG. 8M, before scrolling the user interface objects, user interface objects S1-S12 are not displayed, while in FIG. 8N, after the scrolling of the user interface objects, user interface objects S1-S12 are displayed.)

Conversely, in some embodiments, the device reduces the size of an array after detecting a pinching finger gesture (e.g., a two-finger pinching gesture) on a first array in the plurality of arrays. For example, in FIG. 8N, the device detects simultaneous contacts (e.g., 8108-1 and 8110-1 on the “School garden” array 8054 in FIG. 8N) and movement (e.g., 8112 and 8114 in FIG. 8N) of the contacts to a new location (e.g., 8108-2 and 8110-2 in FIG. 8O). In response to detecting the pinching finger gesture on the first array (e.g., 8054 in FIG. 8N) in the plurality of arrays, the device reduces the size of user interface objects (e.g., images S1-S30 in FIG. 8N are reduced in size as displayed as S1-S30 in FIG. 8O) in the first array without reducing the size of the user interface objects in arrays other than the first array. For example, the user interface objects (e.g., images D1-D36) in the “Day at the zoo” array in FIG. 8M are the same size as the user interface objects (e.g., images D1-D36) in the “Day at the zoo” array 8052 in FIG. 8O after the zoom out operation has been performed. In some embodiments, the user interface objects in the first array are reduced in size down to a predetermined minimum size. In some embodiments, the user interface objects in the first army are reduced in size by the same amount. In some embodiments, when there is a representative user interface object for the array (e.g., image S33-r in FIG. 8M) the representative user interface object is also resized (e.g., reduced in size).

In some embodiments, the user interface objects are resized about a centroid of the simultaneous user interface contacts (e.g., 8108-2 and 8110-2 in FIG. 8O). For example, when the simultaneous contacts are proximate to a user interface object (e.g., S17 in FIG. 8O) when they are initially detected by the device, as the device resizes the user interface objects, the user interface object (e.g., image S17) which is proximate to the initial location of the simultaneous contacts (e.g., 8108-1 and 8110-1 in FIG. 8N) is moved so as to remain proximate to the user interface contacts. For example, in FIG. 8O, image S17 remains in between the two simultaneous contacts, even though this means that the user interface objects are “pulled” off center. In other words, the user interface objects “under” the pinching gesture behave as though they are on a sheet of rubber that is being contracted in accordance with the pinch, but is “stuck” under the contacts. In this embodiment, when the device detects a lift off of the contacts (e.g., 8108-2 and 8110-2 in FIG. 8O), the device moves (e.g., 8116 in FIG. 8O) array of user interface objects so as to align the array with a vertical edge that other arrays are aligned with (FIG. 8P).

In some embodiments, the device detects (1440) activation of a respective representative user interface object toggle icon (e.g., icon 8056 in FIG. 8P) for a respective array (e.g., detecting a finger tap gesture 8118 in FIG. 8P or a stylus tap gesture on the toggle icon). In response to detecting activation of the respective representative user interface object toggle icon, the device toggles display of the respective representative user interface object for the respective array. For example, in FIG. 8P a representative image S33-r is displayed with the “School garden” array 8054. As shown in FIG. 8Q, in response to activation of toggle icon 8056, the device ceases to display the representative image S33-r.

In some embodiments, in response to detecting activation of the respective representative user interface object toggle icon (e.g., 5086 in FIG. 8P), the device rearranges (1442) user interface objects in the respective array. For example, when the representative user interface object is displayed, the user interface objects in the respective array are displayed with the same height and the same width, and the objects are ordered sequentially by columns (e.g., successive user interface objects are ordered top-to-bottom, left-to-right in the array, as illustrated in FIG. 8P). But when the representative user interface object is not displayed, the user interface objects in the respective array are displayed with the same height and the objects are ordered sequentially by rows (e.g., successive user interface objects are ordered left-to-right, top-to-bottom in the array, as illustrated in FIG. 8Q).

In some embodiments, a single array in the plurality of arrays is rearranged in response to multifinger gestures as described above with respect to FIGS. 7A-7O and 13A-13B.

In some embodiments, while the single array is displayed without the representative user interface object (e.g., as in FIG. 8Q) the device detects a second activation of the respective representative user interface object toggle icon (e.g., 8056 in FIG. 8Q) for a respective array (e.g., by detecting a mouse click while a cursor 8120 in FIG. 8Q is positioned over the respective representative user interface object toggle icon, a finger tap gesture, or a stylus tap gesture on the toggle icon). For example, in FIG. 8Q, representative image S33-r is not displayed with the “School garden” array 8054, while in FIG. 8R, after the second activation of the toggle icon 8056, the device displays the representative image S33-r.

In some embodiments, the device detects (1444) a first input by the user (e.g., a press and hold finger contact 8122-1 in FIG. 8R or stylus contact) on a first user interface object (e.g., image D17 in FIG. 8R) in a first array (e.g., 8052 in FIG. 8R) on the touch screen display. While continuing to detect the first input by the user: the device detects movement (e.g., 8124 in FIG. 8S) of the first input by the user across the touch screen display to an area (e.g., 8126 in FIG. 8S) associated with a second array (e.g., 8054 in FIG. 8S) on the touch screen display (e.g., an area containing the user interface objects in the second array); the device moves the first user interface object (e.g., from D17 to D17′ in FIG. 8S) in accordance with the movement of the first input by the user across the touch screen display to the area (e.g., 8126 in FIG. 8S) associated with the second array (e.g., 8054 in FIG. 8S) on the touch screen display; the device detects lift off of the first input by the user (e.g., lift off of the first finger contact 8122-2 in FIG. 8S or the stylus contact) from the area 8126 associated with the second array; and, in response to detecting lift off of the first input by the user from the area associated with the second array, the device associates the first user interface object with the second array (e.g., adds image D17 to the “School garden” event array 8054) and displays the first user interface object in the second array (e.g., as shown in FIGS. 8T-8U, where D17 moves 8128 into array 8054).

In some embodiments, the device displays (1446) a residual image of the first user interface object in the first array on the touch screen display (e.g., shaded user interface object D17 in FIGS. 8S-8T). In some embodiments, the residual image is displayed in the first array while the first input (e.g., contact 8122-1 in FIG. 8S) by the user is still detected on the touch screen display, but the residual image ceases to be displayed in response to detecting lift off of the first input (e.g., lift off of contact 8122-2 in FIG. 8S).

In some embodiments, in response to detecting lift off of the first input (e.g., lift off of contact 8122-2 in FIG. 8S) by the user (e.g., lift off of a first finger contact or stylus contact) from the area (e.g., 8126 in FIG. 8S) associated with the second array (e.g., 8054 in FIG. 8S), the device also displays (1448) the first user interface object in the first array and ceases to display the residual image of the first user interface object in the first array (i.e., the first user interface object is displayed in both the first array 8052 and the second array 8054). For example, in FIG. 8U, the user interface object D17 is displayed in both the first array 8052 and the second array 8054.

In some embodiments, in response to detecting lift off of the first input (e.g., lift off of contact 8122-2 in FIG. 8S) by the user (e.g., lift off of the first finger contact or stylus contact by the user) from the area (e.g., 8126 in FIG. 8S) associated with the second array (e.g., 8054 in FIG. 8S), the device disassociates (1450) the first user interface object from the first array and ceases to display the residual image of the first user interface object in the first array. For example in FIG. 8V, the user interface object D17 is displayed only in the second array 8054, and the user interface object D17 has been removed from the first array 8052. In some embodiments, the remaining user interface objects (e.g., images D1-D16, D18-D36) in the first array are rearranged to fill in the space left by the removed user interface object, as shown in FIG. 8V, while remaining in time/number order.

In some embodiments, a group of selected objects is formed and then the group is moved/acted upon, as described above with respect to FIGS. 6A-6X, 11A-11B, and 12A-12B.

In some embodiments, the device detects (1452) activation of a respective array name icon that corresponds to a respective array (e.g., array 8052 in FIG. 8V) in the plurality of arrays (e.g., detecting a press and hold finger contact input 8130-1 or stylus contact by the user on the “Day at the zoo” array name icon 8132 in FIG. 8V, which is displayed adjacent to a respective representative user interface object toggle icon). In response to detecting activation of the respective array name icon (e.g., “Day at the zoo” 8132 in FIG. 8V) that corresponds to the respective array (e.g., 8052 in FIG. 8V), the device displays an animation of user interface objects in the respective array moving into a respective representative user interface object for the respective array. The animation indicates to a user that all of the user interface objects in the array are being grouped together. For example, FIG. 8W, illustrates an animation of images D1′, D2′, D3′, D4′, D5′, D6′, D7′, D8′, D9′, D12′, D15′, D19′, D25′, D28′, D31′, D36′, etc. moving towards representative image D7-r, while residual user interface objects are displayed in the original locations of the user interface objects (e.g., shaded user interface objects D32, D33, D34, D35, D36, etc. in FIG. 8W). It should be understood that, in this example, all of the user interface objects in array 8052 are moving into representative user interface object D7-r, however, some of the user interface objects are shown as covering other user interface objects, and thus, not all of the user interface objects are visible in FIG. 8W.

The device detects movement (e.g., 8132 in FIG. 8X) of an input by the user (e.g., a finger contact 8130-1 or stylus contact) from the array name icon (e.g., 8132 in FIG. 8X) to a destination object or an area associated with a destination object (e.g., area 8134 in FIG. 8X). The device moves the respective representative user interface object (e.g., from D7-r to D7-r′ in FIG. 8X) in accordance with the movement (e.g., 8132 in FIG. 8X) of the input (e.g., contact 8130-1 moves to a new contact location 8130-2 in FIG. 8X) by the user across the touch screen display to the destination object or the area associated with a destination object (e.g., the area associated with the “Family reunion” event icon 8010 in FIG. 8X). In some embodiments, a counter (e.g., 8136 in FIG. 8X) with the number (e.g., “35”) of user interface objects in the respective array is also displayed.

The device detects lift off of the input (e.g., contact 8130-2 is present in FIG. 8X and has lifted off in FIG. 8Y) by the user (e.g., lift off of the finger contact or stylus contact) from the touch screen display at the destination object or at the area (e.g., 8134 in FIG. 8Y) associated with a destination object. In response to detecting lift off of the input by the user from the touch screen display at the destination object or at the area (e.g., 8134 in FIG. 8Y) associated with the destination object, the device performs an action on the user interface objects in the respective array. The action is associated with the destination object. Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document.

In some embodiments, the action is (1454) performed on all of the user interface objects in the respective array (e.g., all of the user interface objects from the “Day at the zoo” array 8052 are made part of the “Family reunion” array 8064, as illustrated in FIG. 8AA).

In some embodiments, in response to detecting activation of the respective array name icon that corresponds to the respective array, the device displays (1456) a counter (e.g., 8136 in FIG. 8X) with the number of user interface objects (e.g., “35”) in the respective array.

In some embodiments, in response to detecting activation of the respective array name icon (e.g., contact 8130-1 with array name icon “Day at the zoo” 8132 in FIG. 8X) that corresponds to the respective array, the device displays (1458) residual images (e.g., shaded images D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, D13, D14, D15, D16, D18, D19, D20, D21, D22, D23, D24, D25, D26, D27, D28, D29, D30, D31, D32, D33, D34, D35, D36 in FIGS. 8W-8Z) of user interface objects in the respective array.

In some embodiments, in response to detecting lift off of the input by the user (e.g., lift off of the finger contact or stylus contact) from the touch screen display at the destination object or at the area associated with the destination object, the device displays (1460) the user interface objects in the respective array and ceases to display the residual images of user interface objects in the respective array (i.e., the user interface objects replace their residual images in the respective array). For example, in FIGS. 8Y-8AA, after the device detects lift off of the contact 8130-2 (FIG. 8Y), the images D1-D36 replace their residual images in array 8052. In addition, the device replaces display of the representative user interface object (e.g., D7-r′ in FIG. 8Y) and the counter (e.g., 8136 in FIG. 8Y) with representations of the user interface objects (e.g., D1′, D2′, D3′, D4′, D5′, D6′, 17′, D8′, D9′, D10′, D11′, D12′, D13′, D14′, D15′, D16′, D18′, D19′, D20′, D21′, D22′, D23′, D24′, D25′, D26′, D27′, D28′, D29′, D30′, D31′, D32′, D33′, D34′, D35′, D36′ in FIG. 8Z). In some embodiments, the device displays an animation of these user interface objects moving into the array associated with the destination object (e.g., “Family reunion” array 8064). In FIG. AA, after the animation has completed, user interface objects D1′, D2′, D3′, D4′, D5′, D6′, D7′, D8′, D9′, D10′, D11′, D12′, D13′, D14′, D15′, D16′, D18′, D19′, D20′, D21′, D22′, D23′, D24′, D25′, D26′, D27′, D28′, D29′, 130′, D31′, D32′, D33′. D34′, D35′, D36′ are shown as part of the “Family reunion” array 8064, and corresponding user interface objects D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, D13, D14, D15, D16, D18, D19, D20, D21, D22, D23, D24, D25, D26, D27, D28, D29, D30, D31, D32, D33, D34, D35, D36 are simultaneously shown in the “Day at the zoo array” 8052.

In some embodiments, in response to detecting movement of the input by the user from the array name icon, the device displays (1464) a residual image of the respective representative user interface object (e.g., shaded representative user interface object D7-r in FIGS. 8X-8Z). In some embodiments, the residual image of the respective representative user interface object is (1466) displayed adjacent to a respective representative user interface object toggle icon (e.g., 8138 in FIG. 8Z).

In some embodiments, the device detects (1468) activation of a menu category icon (e.g., activation of menu category icon “Events” 8002 for a plurality of array name icons for events 8004, 8006, 8008, 8010, 8012, 8014, 8016, 8018, 8020, 8022, 8024 in FIG. 8AA by a finger tap gesture 8140, stylus gesture, or mouse click on the menu category icon). In response to detecting activation of the menu category icon (e.g., “Events” 8002), the device displays a plurality of representative user interface objects for respective arrays in a menu category that corresponds to the menu category icon, as shown in FIG. 8CC.

In some embodiments, displaying the plurality of representative user interface objects includes overlaying (1470) the plurality of representative user interface objects on user interface objects displayed on the touch screen display immediately prior to detecting activation of the menu category icon. For example, in FIG. 8CC, a plurality of representative user interface objects (e.g., representative images B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r) are displayed overlaid on shaded images F1-F17, D1′-D16′, and D18′-D36′. In some cases, the representative objects appear as though they are layered on top of the previously displayed user interface. In some embodiments, the device displays an animation where the representative user interface objects (e.g., B1-r, D7-r, S33-r. F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r) are shown coming in from the edges (e.g., top, bottom, right and left sides) of the display and shrinking to fit onto the display. Thus, in FIG. 8BB, the representative user interface objects (e.g., B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r) are larger than the corresponding representative user interface objects in FIG. 8CC, and the user interface objects that are adjacent to the edges of the touch screen display (e.g., B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, H27-r and P6-r) are only partially displayed. Additionally, in some embodiments, the representative user interface objects are initially displayed at a low opacity (e.g., 0% opacity or 10% opacity) and the opacity of the representative user interface objects is gradually increased as the representative user interface objects are reduced in size and moved onto the touch screen display.

In some embodiments, displaying the plurality of representative user interface objects (e.g., B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIG. 8DD) includes ceasing (1472) to display user interface objects displayed on the touch screen display immediately prior to detecting activation of the menu category icon, as shown in FIG. 8DD. In other words, the user interface objects displayed on the touch screen display immediately prior to detecting activation of the menu category icon are replaced by display of the plurality of representative user interface objects for respective arrays in the menu category that corresponds to the activated menu category icon (e.g., as shown in FIG. 5DD).

In some embodiments, only the plurality of representative user interface objects (e.g., B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIG. 8DD) for respective arrays in the menu category that corresponds to the activated menu category icon are (1474) displayed on the touch screen display (e.g., as shown in FIG. 8DD).

In some embodiments, the device detects (1476) an input by the user (e.g., a finger tap gesture 8142 in FIG. 8CC, stylus gesture, or mouse click) on a first representative user interface object (e.g., representative image B1-r in FIG. 8CC) in the plurality of representative user interface objects (e.g., representative images B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIG. 8CC) for respective arrays in the menu category that corresponds to the activated menu category icon (e.g., 8002 in FIG. 8AA). In response to detecting the input by the user on the first representative user interface object, the device ceases to display the plurality of representative user interface objects and displays an array (e.g., the “Birthday” array 8144 in FIG. 8EE) of user interface objects (e.g., images B1, B2, B3, B4, B6, B7, B8, B9, B10, B11, B13, B14, B15, B16, B17, B18, B19, B20, B21, B22, B23, B24, 825, B26, B27) that correspond to the first representative user interface object (e.g., B1-r in FIG. 8CC).

In some embodiments, in response to detecting the input by the user on the first representative user interface object (e.g., representative image B1-r in FIG. 8CC), the device displays (1478) the first representative user interface object adjacent to the array (e.g., “Birthday” array 8144 in FIG. 8EE) of user interface objects that corresponds to the first representative user interface object (e.g., representative image B1-r in FIG. 8EE).

In some embodiments, in response to detecting the input by the user on the first representative user interface object, the device displays (1480) arrays (e.g., “Day at the zoo” array 8052 in FIG. 8EE) of user interface objects (e.g., images D1, D2, D3, D4, D5, D6, D7, D8, D9, D10, D11, D12, D13, D14, D15, D16, D18, D19, D20, D21, D22, D23, D24, D25, D26, D27, D28, D29, D30, D31, D32, D33, D34, D35, D36 in FIG. 8EE) that do not correspond to the first representative user interface object (e.g., arrays in the plurality of arrays that are adjacent to the array of user interface objects that corresponds to the first representative user interface object).

In some embodiments, selected object(s) am moved to a destination object (e.g., an item in sidebar menu) while input by the user (e.g., a finger contact or stylus contact) is on the destination object, as described above with respect to FIGS. 5A-5Y and 9A-9D, 10A-10B.

In some embodiments, the device detects (1482) a third input by the user (e.g., a finger contact 8146 in FIG. 8FF or stylus contact) on a destination object (e.g., “Adorable children” label icon 8032 in FIG. 8FF). While continuing to detect the third input (e.g., contact 8146 in FIGS. 8FF-8LL) by the user on the destination object (e.g., “Adorable children” label icon 8032 in FIG. 8FF-8LL), the device detects a fourth input by the user on an array name icon (e.g., a finger tap gesture 8148, stylus gesture, or mouse click by the user on an array name icon 8132 in FIG. 8GG displayed adjacent to a respective representative user interface object toggle icon e.g., 8138 in FIG. 8GG). In response to detecting the fourth input (e.g., tap gesture 8148 in FIG. 8GG) by the user on the array name icon (e.g., 8132 in FIG. 8GG), the device performs an action on all user interface objects (e.g., images D1-D16, D18-D36 in FIG. 8GG) in an array (e.g., “Day at the zoo” array 8052 in FIG. 8GG) that corresponds to the array name icon (e.g., 8132 in FIG. 8GG). The action is associated with the destination object (e.g., “Adorable children” label icon 8032 in FIG. 8GG). In some embodiments, the action is a preparatory action, such as preparing to perform an action that will occur upon detecting lift off of the third input (e.g., lift off of the third finger contact 8416 in FIG. 8GG by the user) from the destination object. Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document.

In some embodiments, in response to detecting the fourth input (e.g., tap gesture 8148 in FIG. 8GG) by the user on the array name icon (e.g., 8132 in FIG. 8GG), the device displays (1484) an animation of user interface objects in the array (e.g., 8052 in FIGS. 8GG-8II) that corresponds to the array name icon moving from respective initial object positions into the destination object. For example, in FIGS. 8HH and 8II, the device displays representations of the images D1-D16 and D18-D36 moving into the destination object (e.g., 8032 in FIGS. 8HH and 8II). In this example, as each user interface object (e.g., D11′ in FIG. 8HH) begins to move towards the destination object (e.g., 8032 in FIG. 8HH), the device resizes the user interface object so as to match the dimensions of the destination object (e.g., 8032 in FIG. 8HH). In the case of image D11′, the object is taller and narrower than the destination object, so in a subsequent frame of the animation (shown in FIG. 8II) the user interface object D11′ is has been resized so that it is shorter and wider than the original user interface object D11 (in FIG. 8GG, before the animation was displayed). This process is performed for some or all of the user interface objects in the array (e.g., 8052 in FIGS. 8HH and 8II). In some embodiments this process is also performed for the representative user interface object (e.g., D7-r′ in FIGS. 8HH and 8II). The animation indicates to a user that an action associated with the destination object will be applied to the user interface objects in this array.

In some embodiments, in response to detecting the fourth input (e.g., tap gesture 8148 in FIG. 8G) by the user on the array name icon (e.g., 8132 in FIG. 8GG), the device displays (1486) respective residual images (e.g., shaded images D1, D7, D16, D18, D20, D25, etc. in FIGS. 8II and 8JJ) of respective user interface objects at respective initial user interface object positions on the touch screen display (e.g., respective positions of D1, D7, D16, D18, D20, D25, etc. in FIG. 8GG).

In some embodiments, the device detects (1488) a fifth input (e.g., a finger tap gesture 8150 (FIG. 83J), stylus gesture, or mouse click) on a respective residual image (e.g., shaded image D12 in FIG. 8JJ) of a respective user interface object at a respective initial user interface object position on the touch screen display while continuing to detect the third input (e.g., contact 8146 in FIG. 8JJ) by the user on the destination object (e.g., “Adorable children” icon 8032 in FIG. 8JJ). In response to detecting the fifth input (e.g., tap gesture 8150 in FIG. 8JJ) by the user on the respective residual image (e.g., shaded image D12 in FIG. 83J) of the respective user interface object at the respective initial user interface object position on the touch screen display, the device undoes the action performed on the respective user interface object and displays the respective user interface object at the respective initial user interface object position. For example, image D12 will not be labeled “Adorable children” and the residual shaded image of D12 (FIG. 8JJ) is replaced by the original unshaded image of D12 (FIG. 8LL).

In some embodiments, in response to detecting the fifth input by the user on the respective residual image of the respective user interface object at the respective initial user interface object position on the touch screen display, the device displays (1490) an animation of the respective user interface object moving from the destination object back to the respective initial user interface object position. The animation indicates to a user that an action associated with the destination object will not be applied to the respective user interface object. For example FIG. 8KK illustrates an exemplary an animation of undoing the prior movement of user interface object D12 from its initial position to the destination object “Adorable children” 5030 (as shown in FIGS. 8HH-8II). In this animation, the device moves user interface object D12 along a path (e.g., 8152 in FIG. 8KK) from the location at the destination object 5032 back to its original position (e.g., image D12 in FIG. 8KK). In one embodiment, as the user interface object moves along the path, the user interface object is initially displayed as a resized representation so as to match the size of the destination object. An illustrative example of the movement and resizing (e.g., from D12″″ to D12′″ to D12″ to D12′ in FIG. 8KK and finally to D12 in FIG. 8LL) of the user interface object is shown in FIGS. 8KK-8LL. In this example, destination object (e.g., 8032 in FIG. 8KK) is larger along the horizontal dimension (i.e., longer) and smaller along the vertical dimension (i.e., shorter) than the image D12. Thus, as illustrated in FIG. 8KK, the user interface object is initially displayed as a representation of the user interface object (e.g., 12M′″) that is stretched horizontally and compressed vertically compared to the original user interface object (e.g., image D12). As the user interface object moves (e.g., from 12″″ to D12′″ to D12″ to D12′ and finally to D12) towards the original position of the image D12, the user interface object is compressed horizontally and stretched vertically so that it returns to the dimensions of the original image D12. It should be understood that, typically the various resized representations of the user interface object (e.g., D12, D12′, D12″, D12′″ and D12″″ shown in FIGS. 8KK-8LL) are not simultaneously displayed, but are instead displayed in sequence as the user interface object moves along the path 8152 towards the destination object. In some embodiments, where the user interface object includes an image, the image is distorted as the object is resized.

After the device undoes the action performed on the respective user interface object, the respective user interface object is displayed at the initial respective user interface object position (e.g., unshaded image D12, as illustrated in FIG. 8LL).

In some embodiments, the device detects (1491) an input by the user (e.g., a finger contact 8154 in FIG. 8MM or stylus contact) on a user interface object (e.g., image B26 in FIG. 8MM) in an array (e.g., the “Birthday” array 8144 in FIG. 8MM) in the plurality of arrays (e.g., including arrays 8144, 8052 and 8054 in FIG. 8MM). While continuing to detect the input (e.g., contact 8154) by the user on the user interface object in the array in the plurality of arrays, for a plurality of destination objects (e.g., array name icons 8006 and 8008, and label 8032 in sidebar menu 8156, FIG. 8MM), the device detects a respective input by the user (e.g., a finger or stylus gesture such as a tap gestures 8158, 8160, and 8162 in FIG. 8MM) on a respective destination object. In response to each respective input by the user on each respective destination object, the device performs a respective action on the user interface object in the array in the plurality of arrays. The respective action is associated with the respective destination object. In some embodiments, the respective action is a preparatory action, such as preparing to perform an action that will occur upon detecting lift off of the input by the user (e.g., lift off of the finger contact 8154 in FIG. 8MM) from the user interface object in the array. Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document.

For example, in FIG. 8MM, while continuing to detect finger contact 8154 on image B26, the device detects three respective user inputs (e.g., tap gesture 8158, tap gesture 8160, and tap gesture 8162) associated with respective destination objects (e.g., “Day at the zoo” array name destination object 8006, “School garden” array name destination object 8008, and “Adorable children” label destination object 8032.) In response to the each of the respective inputs, the device performs an action associated with the input. For example, in response to the tap gesture 8158 on the “Day at the zoo” array name 8006, the device makes image B26 part of the “Day at the zoo” array 8052 (FIG. 8NN). In response to the tap gesture 8160 on the “School garden” array name 8008, the device makes image B26 part of the “School garden” array 8054 (FIG. 8NN). In response to the tap gesture 8162 on the “Adorable children” label 8032, the device adds the label “Adorable children” to image B26. Thus, the user is able to perform multiple actions on a single user interface object by maintaining one input (e.g., contact 8154 in FIG. 8MM) on the single user interface object and simultaneously providing other inputs (e.g., tap gestures 8158, 8160, and 8162 in FIG. 8MM) on destination objects (e.g., 8006, 8008 and 8032 in FIG. 8MM) in a menu (e.g., 8156 in FIG. 8MM).

In some embodiments, in response to each respective input by the user on each respective destination object, the device displays (1492) a respective animation of the user interface object in the array moving from a respective initial object position into the respective destination object, as described previously with reference to FIGS. 5E, 5K-5L, 5O, 5P and/or 5Q depending on the type of action performed and the number of objects on which the action is being performed.

In some embodiments, the device detects (1493) an input (e.g., a finger or stylus gesture such as a double tap gesture 8164 in FIG. 8NN) by the user on a first user interface object (e.g., image D29 in FIG. 8NN) in a first array (e.g., “Day at the zoo” array 8052 in FIG. 8NN) in the plurality of arrays (e.g., including arrays 8144, 8052, and 8054 in FIG. 8NN). In response to detecting the input by the user on the first user interface object in the first array in the plurality of arrays, the device displays a first enlarged image (e.g., image D29-f in FIG. 8OO) that corresponds to the first user interface object (e.g., a full-screen image of a photograph or a preview image of an electronic document file that corresponds to user interface object D29 in FIG. 8NN).

The device detects a horizontal (or substantially horizontal) swipe gesture (e.g., contact 8166 followed by movement 8168 of the contact in a direction that is substantially horizontal in FIG. 8OO) by the user on the first enlarged image (e.g., image D29-f in FIG. 800) that corresponds to the first user interface object (e.g., image D29 in FIG. 8NN). In response to detecting the horizontal (or substantially horizontal) swipe gesture by the user on the first enlarged image that corresponds to the user interface object, the device displays a second enlarged image (e.g., image D30-f in FIGS. 8PP and 8QQ) of a second user interface object (e.g., image D30 in FIG. 8NN) in the first array that is adjacent to the first user interface object (e.g., image D29 in FIG. 8NN) in the first array (e.g., “Day at the zoo” array 8052 in FIG. 8NN). In some embodiments, the device displays an animation of the first enlarged image (e.g., image D29-f in FIG. 800) sliding off of the display and being replaced with the second enlarged image (e.g., image D30-f in FIG. 8PP), as shown by the progression of FIGS. 8OO to 8PP to 8QQ. In FIG. 8QQ, the first enlarged image D29-f in FIGS. 800-8PP has been completely replaced with the second enlarged image D30-f.

In some embodiments, the device detects (1494) a vertical (or substantially vertical) swipe gesture by the user on the first enlarged image (e.g., D29-f in FIG. 8OO). In response to detecting the vertical (or substantially vertical) swipe gesture by the user on the first enlarged image, the device scrolls the first enlarged image (not shown).

In some embodiments, the device detects (1495) an input by the user (e.g., a press and hold gesture 8172 in FIG. 8OO) on the first enlarged image (e.g., image D29-f in FIG. 8OO). In response to detecting the input by the user on the first enlarged image, the device displays the user interface objects in the first array in a cover flow mode of display. For example, in FIG. 8RR, the enlarged images of the user interface objects in the “Day at the zoo” array 8052 (FIG. 8NN) are displayed in cover flow mode. In some embodiments, cover flow mode is a mode where the currently displayed user interface item (e.g., image D29-f in FIG. 8RR) is displayed to the user, while skewed representations of adjacent user interface items (e.g., images D28-f and D30-f in FIG. 8RR) are displayed on each side of the currently displayed user interface item. Cover flow mode is described in U.S. patent application Ser. No. 11/519,460, “Media Manager With Integrated Browsers,” filed Sep. 11, 2006, which is hereby incorporated by reference herein in its entirety. In response to a swipe gesture (not shown) the device scrolls through the enlarged representations of user interface items in the cover flow view, displaying a current enlarged representation of a user interface item in the center of the display (e.g., image D29-f in FIG. 8RR). In some embodiments, the speed of the scrolling is determined based on the speed of the swipe gesture.

In some embodiments, the device detects (1496) an input by the user (e.g., a finger or stylus contact 8174-1 in FIG. 8SS) on a first user interface object in a first array (e.g., image D22 in the “Day at the zoo” array 8052 in FIGS. 8SS-8UU) of user interface objects (e.g., images D1-D16, D18-136) in the plurality of arrays (e.g., including arrays 8144 and 8052 in FIGS. 8SS-8UU). The device detects movement (e.g., movement 8176 in FIG. 8SS) of the input (e.g., contact 8174) by the user to a representative user interface object (e.g., representative image D7-r in FIG. 8SS) for the first array (e.g., 8052 in FIG. 8SS) of user interface objects. The device detects lift off of the input by the user (e.g., lift off of the finger contact or stylus contact 8174-2) from the representative user interface object for the first array of user interface objects. In response to detecting lift off of the input by the user from the representative user interface object (e.g., representative image D7-r in FIG. 8TT) for the first array of user interface objects, the device makes the first user interface object the representative user interface object (e.g., representative image D22-r in FIG. 8UU) for the first array of user interface objects (e.g., 8052 in FIG. 8UU).

For example, the device detects a contact 8174-1 with image D22 in FIG. 8SS, and movement 8176 of the contact (e.g., from 8174-1 to 8174-2 in FIG. 8SS) to the current representative image D7-r, which is a representation of user interface object D7 (e.g., an enlarged version of D7). In the present example, in FIG. 8TT, the device ceases to detect the contact 8174-2 with image D22′ while the contact is located over the current representative image D7-r. In some embodiments, when the device detects a release of the contact while it is over the current representative user interface object, the device displays an animation (e.g., image D22′ expanding upwards and to the left, as shown in FIG. 8TT) of replacing the current representative user interface object (e.g., representative image D7-r in FIG. 8TT) with a new representative user interface object (e.g., representative image D22-r in FIG. 8UU, which is a representation of image D22, such as an enlarged version of image D22). In FIG. 8UU, the “Day at the zoo” array 8052 is shown with a new representative user interface object, namely representative image D22-r.

FIGS. 15A-15B are flow diagrams illustrating a method 1500 of performing an action on user interface objects in an array in accordance with some embodiments. The method 1500 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 8V-8AA). Some operations in method 1500 may be combined and/or the order of some operations may be changed.

As described below, the method 1500 provides an intuitive way to manipulate all user interface objects in an array of user interface objects at a computing device with a touch screen display. The method reduces the cognitive burden on a user when performing the same action on all user interface objects in an array of user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manipulate all user interface objects in an array of user interface objects faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1502) on the touch screen display at least one destination object (e.g., an array name icon in a list or menu of such icons) and at least a subset of a plurality of arrays (e.g., arrays 8052 and 8054 in FIG. 8V) of user interface objects. Depending on the number of arrays, it may not be possible to simultaneously display every array in the plurality of arrays. In such cases, a subset of the plurality of arrays is displayed and different subsets may be viewed by scrolling the plurality of arrays (e.g., in response to detecting a first finger swipe gesture on the touch screen display, such as a vertical or substantially vertical finger swipe gesture), as described in greater detail above with reference to FIGS. 8A-8F.

The device detects (1504) activation of a respective array name icon that corresponds to a respective array (e.g., array 8052 in FIG. 8V) in the plurality of arrays (e.g., detecting a press and hold finger contact input 8130-1 or stylus contact by the user on the “Day at the zoo” array name icon 8132 in FIG. 8V, which is displayed adjacent to a respective representative user interface object toggle icon).

In response to detecting activation of the respective array name icon that corresponds to the respective array, the device displays (1506) an animation of user interface objects in the respective array moving into a respective representative user interface object (e.g., D7-r in FIG. 8W) for the respective array (e.g., the “Day at the zoo” array 8052 in FIG. 8W), as described in greater detail above with reference to FIG. 8W.

In some embodiments, in response to detecting activation of the respective array name icon (e.g., 8132 in FIG. 8V) that corresponds to the respective array, the device displays (1508) residual images (e.g., shaded images D1-D34 in FIG. 8Y, as described in greater detail above with reference to FIGS. 8W-8Y) of user interface objects in the respective array (e.g., 8052 in FIG. 8V).

In some embodiments, in response to detecting activation of the respective array name icon that corresponds to the respective array, the device displays (1510) a counter (e.g., 8136 in FIG. 8X) with the number of user interface objects (e.g., “35”) in the respective array.

The device detects (1512) movement (e.g., 8132 in FIG. 8X) of an input by the user (e.g., a finger contact or stylus contact) from the array name icon (e.g., 8132 in FIG. 8X) to a destination object or an area (e.g., 8134 in FIGS. 8X-8Y) associated with a destination object, as described in greater detail above with reference to FIG. 8X.

The device moves (1514) the respective representative user interface object (e.g., representative image D7-r in FIG. 8X) (and, in some embodiments, a counter 8134 with the number of user interface objects in the respective army) in accordance with the movement of the input by the user across the touch screen display to the destination object or the area associated with a destination object, as described in greater detail above with reference to FIG. 8X.

In some embodiments, in response to detecting movement of the input by the user from the array name icon, the device displays (1516) a residual image of the respective representative user interface object (e.g., shaded representative image D7-r in FIG. 8Z). In some embodiments, the residual image of the respective representative user interface object is (1518) displayed adjacent to a respective representative user interface object toggle icon (e.g., icon 8138 in FIG. 8Z).

The device detects (1520) lift off of the input by the user (e.g., lift off of the finger contact or stylus contact) from the touch screen display at the destination object or at the area (e.g., 8134 in FIG. 8Y) associated with a destination object.

In response to detecting lift off of the input by the user from the touch screen display at the destination object or at the area associated with the destination object, the device performs (1522) an action on the user interface objects in the respective array. The action is associated with the destination object. Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder; and printing/publishing a copy of the digital content or electronic document, as described in greater detail above with reference to FIGS. 8Y-8AA.

In some embodiments, the action is (1524) performed on all of the user interface objects in the respective array (e.g., on all of the images D1-D16, D81-D36 in array 8052 in FIG. 8V).

In some embodiments, in response to detecting lift off of the input by the user (e.g., lift off of the finger contact 8130-2 in FIG. 8Y or stylus contact) from the touch screen display at the destination object or at the area (e.g., 8134 in FIG. 8Y) associated with the destination object, the device displays (1526) the user interface objects in the respective array (e.g., 8064 in FIG. 8AA) and ceases to display the residual images of user interface objects in the respective array (i.e., the user interface objects replace their residual images in the respective array as shown in FIG. 8AA), as described in greater detail above with reference to FIGS. 8Y-8AA.

In some embodiments, in response to detecting lift off of the input by the user (e.g., lift off of the finger contact 8130-2 in FIG. 8Y or stylus contact) from the touch screen display at the destination object or at the area (e.g., 8134 in FIG. 8Y) associated with the destination object, the device disassociates (1528) the user interface objects from the respective array and ceases to display the residual images of the user interface objects in the respective array (not shown).

FIGS. 16A-16B are flow diagrams illustrating a method 1600 of using representative user interface objects for respective arrays in a menu category to select an array in accordance with some embodiments. The method 1600 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 8AA-8EE). Some operations in method 1600 may be combined and/or the order of some operations may be changed.

As described below, the method 1600 provides an intuitive way to quickly find and select an array in a plurality of arrays at a computing device with a touch screen display. The method reduces the cognitive burden on a user when trying to find a particular array in a plurality of arrays, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to find a particular array faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1602) on the touch screen display at least one destination object (e.g., an array name icon in a list or menu of such icons) and at least a subset of a plurality of arrays of user interface objects. Depending on the number of arrays, it may not be possible to simultaneously display every array in the plurality of arrays. In such cases, a subset of the plurality of arrays is displayed and different subsets may be viewed by scrolling the plurality of arrays (e.g., in response to detecting a first finger swipe gesture on the touch screen display, such as a vertical or substantially vertical finger swipe gesture).

The device detects (1604) activation of a menu category icon (e.g., activation of menu category icon “Events” 8002 for a plurality of array name icons for events 8004, 8006, 8008, 8010, 8012, 8014, 8016, 8018, 8020, 8022, 8024 in FIG. 8AA by a finger tap gesture 8140, stylus gesture, or mouse click on the menu category icon).

In response to detecting activation of the menu category icon (e.g., “Events” 8002), the device displays (1606) a plurality of representative user interface objects for respective arrays in a menu category that corresponds to the menu category icon, (e.g., representative images B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIGS. 8BB-8DD).

In some embodiments, displaying (1608) the plurality of representative user interface objects includes overlaying the plurality of representative user interface objects (e.g., representative images B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIGS. 8BB-8CC) on user interface objects displayed on the touch screen display immediately prior to detecting activation of the menu category icon, as described in greater detail above with reference to FIGS. 8BB-8CC. In some embodiments, displaying the plurality of representative user interface objects includes ceasing (1610) to display user interface objects displayed on the touch screen display immediately prior to detecting activation of the menu category icon. In other words, the user interface objects displayed on the touch screen display immediately prior to detecting activation of the menu category icon are replaced by display of the plurality of representative user interface objects (e.g., representative images B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, RI 1-r, H27-r and P6-r in FIG. 8DD) for respective arrays in the menu category that corresponds to the activated menu category icon, as described in greater detail above with reference to FIG. 8DD.

In some embodiments, only the plurality of representative user interface objects for respective arrays in the menu category that corresponds to the activated menu category icon are (1612) displayed on the touch screen display. For example in FIGS. 8BB-8CC the device displays representative user interface objects for a plurality of the “Events” which include arrays of user interface objects. Similarly, if the “Labels” category icon 8026 (FIG. 8A) were selected, the device would display a representative user interface object for each of a plurality of the labels (e.g., a representative user interface object for the label “Little Wesley” and a representative user interface object for the label “Adorable children”), where selecting the representative user interface object for a respective label would display an array of user interface objects associated with the respective label.

In some embodiments, the device detects (1614) an input by the user (e.g., a finger tap gesture e.g., 8142 in FIG. 8CC, stylus gesture, or mouse click) on a first representative user interface object (e.g., representative image B1-r in FIG. 8CC) in the plurality of representative user interface objects for respective arrays in the menu category that corresponds to the activated menu category icon. In response to detecting the input (e.g., tap gesture 8142 in FIG. 8CC) by the user on the first representative user interface object, the device ceases to display the plurality of representative user interface objects (e.g., representative image B1-r, D7-r, S33-r, F8-r, E45-r, V17-r, N5-r, L2-r, R11-r, H27-r and P6-r in FIG. 8CC) and displays an array of user interface objects that corresponds to the first representative user interface object (e.g., images in the “Birthday” array 8144, as shown in FIG. 8EE).

In some embodiments, in response to detecting the input by the user on the first representative user interface object, the device displays (1616) the first representative user interface object (e.g., representative image B1-r in FIG. 8EE) adjacent to the array (e.g., “Birthday” array 8144 in FIG. 8EE) of user interface objects that corresponds to the first representative user interface object.

In some embodiments, in response to detecting the input by the user on the first representative user interface object, the device displays (1618) arrays (e.g., 8052 in FIG. 8EE) of user interface objects that do not correspond to the first representative user interface object (e.g., B1-r in FIG. 8EE). In other words, the device displays arrays in the plurality of arrays that are adjacent to the array of user interface objects that corresponds to the first representative user interface object.

In some embodiments, selected object(s) are moved to a destination object (e.g., an item in sidebar menu) while input by the user (e.g., a finger contact or stylus contact) is on the destination object, as described above with respect to FIGS. 5A-5Y and 9A-9D, 10A-10B.

FIGS. 17A-17B are flow diagrams illustrating a method 1700 of performing an action on user interface objects in an array in accordance with some embodiments. The method 1700 is performed at a computing device (e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1) with a touch screen display (e.g., 112 in FIGS. 8EE8MM). Some operations in method 1700 may be combined and/or the order of some operations may be changed.

As described below, the method 1700 provides an intuitive way to perform an action on all or most user interface objects in one array ofa plurality of arrays at a computing device with a touch screen display. The method reduces the cognitive burden on a user when performing the same action on all or most user interface objects in an array of user interface objects, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to perform the same action on all or most interface object in an array faster and more efficiently conserves power and increases the time between battery charges.

The device simultaneously displays (1702) on the touch screen display at least one destination object (e.g., an array name icon in a list or menu of such icons) and at least a subset of a plurality of arrays (e.g., 8144 and 8052 in FIG. 8FF) of user interface objects. Depending on the number of arrays, it may not be possible to simultaneously display every array in the plurality of arrays. In such cases, a subset of the plurality of arrays is displayed and different subsets may be viewed by scrolling the plurality of arrays (e.g., in response to detecting a first finger swipe gesture on the touch screen display, such as a vertical or substantially vertical finger swipe gesture), as described in greater detail above with reference to FIGS. 8A-8F.

The device detects (1704) a first input by a user (e.g., a finger contact 8146 in FIG. 8FF or stylus contact) on a destination object (e.g., “Adorable children” label icon 8032 in FIG. 8FF).

While continuing to detect the first input (e.g., contact 8146 in FIGS. 8FF-8LL) by the user on the destination object (e.g., “Adorable children” label icon 8032 in FIGS. 8FF-8LL), the device detects (1706) a second input by the user on an array name icon (e.g., a finger tap gesture 8148 in FIG. 8GG, stylus gesture, or mouse click by the user on an array name icon 8132 in FIG. 8GG displayed adjacent to a respective representative user interface object toggle icon 8138 in FIG. 8GG).

In response to detecting the second input (e.g., tap gesture 8148 in FIG. 80G) by the user on the array name icon, the device performs (1708) an action on all user interface objects (e.g., images D1-D16, D18-D36 in FIG. 8GG) in an array (e.g., “Day at the zoo” array 8052 in FIG. 8GG) that corresponds to the array name icon (e.g., 8132 in FIG. 8GG). The action is associated with the destination object (e.g., “Adorable children” label icon 8032 in FIG. 8HH). In some embodiments, the action is a preparatory action, such as preparing to perform an action that will occur upon detecting lift off of the first input (e.g., lift off of the first finger contact 8416 in FIG. 8GG by the user) from the destination object. Exemplary actions include, without limitation: associating a label with digital content or an electronic document; moving digital content or an electronic document from one event to another event; moving digital content or an electronic document to a folder: and printing/publishing a copy of the digital content or electronic document.

In some embodiments, in response to detecting the second input (e.g., tap gesture 8148 in FIG. 8GG) by the user on the array name icon (e.g., 8132 in FIG. 8GG), the device displays (1710) an animation of user interface objects in the array (e.g., 8052 in FIGS. 8GG-8II) that correspond to the array name icon moving from respective initial object positions into the destination object (e.g., 8032 in FIGS. 8GG-8II), as described in greater detail above with reference to FIGS. 80G-8JJ. The animation indicates to a user that an action associated with the destination object will be applied to the user interface objects in this array.

In some embodiments, in response to detecting the second input (e.g., tap gesture 8148 in FIG. 8GG) by the user on the array name icon (e.g., 8132 in FIG. 8GG), the device displays (1712) respective residual images (e.g., shaded images D1-D16 and D18-D36 in FIG. 8JJ) of respective user interface objects at respective initial user interface object positions on the touch screen display.

In some embodiments, the device detects (1714) a third input by the user (e.g., a finger tap gesture 8150 (FIG. 8JJ), stylus gesture, or mouse click) on a respective residual image (e.g., shaded image D12 in FIG. 8JJ) of a respective user interface object at a respective initial user interface object position on the touch screen display while continuing to detect the first input by the user on the destination object (e.g., contact 8146 on “Adorable children” icon 8032 in FIG. 8JJ). In response to detecting the third input (e.g., tap gesture 8150 in FIG. 8JJ) by the user on the respective residual image of the respective user interface object (e.g., shaded image D12 in FIG. 8JJ) at the respective initial user interface object position on the touch screen display, the device undoes the action performed on the respective user interface object and displays the respective user interface object at the respective initial user interface object position, as described in greater detail above with reference to FIGS. 8JJ-4LL. For example, image D12 will not be labeled “Adorable children” and the residual shaded image of D12 (FIG. 8JJ) is replaced by the original unshaded image of D12 (FIG. 8LL).

In some embodiments, in response to detecting the third input (e.g., tap gesture 8150 in FIG. 8JJ) by the user on the respective residual image (e.g., shaded image D12 in FIG. 8JJ) of the respective user interface object at the respective initial user interface object position on the touch screen display, the device displays (1716) an animation of the respective user interface object moving from the destination object back to the respective initial user interface object position, as described in greater detail above with reference to FIG. 8KK. The animation indicates to a user that an action associated with the destination object will not be applied to the respective user interface object.

The steps in the information processing methods described above may be implemented by running one or more functional modules in information processing apparatus such as general purpose processors or application specific chips. These modules, combinations of these modules, and/or their combination with general hardware (e.g., as described above with respect to FIGS. 1A, 1B and 3) are all included within the scope of protection of the invention.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. An electronic device, comprising: a touch-sensitive display;one or more processors; andmemory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the touch-sensitive display, a user interface that includes a plurality of user interface objects, wherein the plurality of user interface objects includes a first user interface object, a second user interface object, and a third user interface object, and wherein the first user interface object is displayed as being selected and the second user interface object and the third user interface object are displayed as being unselected;while displaying the user interface that includes the plurality of user interface objects, detecting a first input that moves across a location associated with the second user interface object and a location associated with the third user interface object; andin response to detecting the first input, displaying the second user interface object and the third user interface object as being selected.
2. The electronic device of claim 1, wherein, in response to detecting the first input, the first user interface object, the second user interface object, and the third user interface object are concurrently displayed as being selected.
3. The electronic device of claim 1, wherein prior to detecting the first input, the second user interface object is displayed with a first appearance and the third user interface object is displayed with a second appearance, the one or more programs further including instructions for: in response to detecting the first input: changing the appearance of the second user interface object from the first appearance to a third appearance that is different from the first appearance; andchanging the appearance of the third user interface object from the second appearance to a fourth appearance that is different than the second appearance.
4. The electronic device of claim 3, the one or more programs further including instructions for: while the second user interface object is displayed with the third appearance, detecting a third input directed to the second user interface object; andin response to detecting the third input directed to the second user interface object, changing the appearance of the second user interface object from the third appearance to the second appearance.
5. The electronic device of claim 1, the one or more programs further including instructions for: while the first user interface object is displayed as being selected and while detecting the first input, detecting movement of the first input from a first position to a second position; andin response to detecting movement of the first input from the first position to the second position, moving display of the first user interface object based on the movement of the first input.
6. The electronic device of claim 1, wherein the first user interface object is displayed at a third position on the user interface prior to detecting the first input, the one or more programs further including instructions for: in response to detecting the first input, displaying a residual image of the first user interface object at the third position on the user interface.
7. The electronic device of claim 1, the one or more programs further including instructions for: while the first user interface object, the second user interface object, and the third user interface object are displayed as being selected and while detecting the first input, detecting liftoff of the first input; andin response to detecting liftoff of the first input, performing an action on the first user interface object, the second user interface object, and the third user interface object.
8. The electronic device of claim 1, the one or more programs further including instructions for: while the first user interface object is displayed as being selected, detecting an input that corresponds to selection of a fourth user interface object; andin response to detecting the input that corresponds to selection of the fourth user interface object, displaying the first user interface object and the fourth user interface object as being grouped together.
9. The electronic device of claim 1, wherein the first input is an input that is moved across the second user interface object and the third user interface object.
10. A method, comprising: at an electronic device having a touch-sensitive display: displaying, on the touch-sensitive display, a user interface that includes a plurality of user interface objects, wherein the plurality of user interface objects includes a first user interface object, a second user interface object, and a third user interface object, and wherein the first user interface object is displayed as being selected and the second user interface object and the third user interface object are displayed as being unselected;while displaying the user interface that includes the plurality of user interface objects, detecting a first input that moves across a location associated with the second user interface object and a location associated with the third user interface object; andin response to detecting the first input, displaying the second user interface object and the third user interface object as being selected.
11. The method of claim 10, wherein, in response to detecting the first input, the first user interface object, the second user interface object, and the third user interface object are concurrently displayed as being selected.
12. The method of claim 10, wherein prior to detecting the first input, the second user interface object is displayed with a first appearance and the third user interface object is displayed with a second appearance, the method further comprising: in response to detecting the first input: changing the appearance of the second user interface object from the first appearance to a third appearance that is different from the first appearance; andchanging the appearance of the third user interface object from the second appearance to a fourth appearance that is different than the second appearance.
13. The method of claim 12, further comprising: while the second user interface object is displayed with the third appearance, detecting a third input directed to the second user interface object; andin response to detecting the third input directed to the second user interface object, changing the appearance of the second user interface object from the third appearance to the second appearance.
14. The method of claim 10, further comprising: while the first user interface object is displayed as being selected and while detecting the first input, detecting movement of the first input from a first position to a second position; andin response to detecting movement of the first input from the first position to the second position, moving display of the first user interface object based on the movement of the first input.
15. The method of claim 10, wherein the first user interface object is displayed at a third position on the user interface prior to detecting the first input, further comprising: in response to detecting the first input, displaying a residual image of the first user interface object at the third position on the user interface.
16. The method of claim 10, further comprising: while the first user interface object, the second user interface object, and the third user interface object are displayed as being selected and while detecting the first input, detecting liftoff of the first input; andin response to detecting liftoff of the first input, performing an action on the first user interface object, the second user interface object, and the third user interface object.
17. The method of claim 10, further comprising: while the first user interface object is displayed as being selected, detecting an input that corresponds to selection of a fourth user interface object; andin response to detecting the input that corresponds to selection of the fourth user interface object, displaying the first user interface object and the fourth user interface object as being grouped together.
18. The method of claim 10, wherein the first input is an input that is moved across the second user interface object and the third user interface object.
19. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a touch-sensitive display, the one or more programs including instructions for: displaying, on the touch-sensitive display, a user interface that includes a plurality of user interface objects, wherein the plurality of user interface objects includes a first user interface object, a second user interface object, and a third user interface object, and wherein the first user interface object is displayed as being selected and the second user interface object and the third user interface object are displayed as being unselected; while displaying the user interface that includes the plurality of user interface objects, detecting a first input that moves across a location associated with the second user interface object and a location associated with the third user interface object; andin response to detecting the first input, displaying the second user interface object and the third user interface object as being selected.
20. The non-transitory computer-readable storage medium of claim 19, wherein, in response to detecting the first input, the first user interface object, the second user interface object, and the third user interface object are concurrently displayed as being selected.
21. The non-transitory computer-readable storage medium of claim 19, wherein prior to detecting the first input, the second user interface object is displayed with a first appearance and the third user interface object is displayed with a second appearance, the one or more programs further including instructions for: in response to detecting the first input: changing the appearance of the second user interface object from the first appearance to a third appearance that is different from the first appearance; andchanging the appearance of the third user interface object from the second appearance to a fourth appearance that is different than the second appearance.
22. The non-transitory computer-readable storage medium of claim 21, the one or more programs further including instructions for: while the second user interface object is displayed with the third appearance, detecting a third input directed to the second user interface object; andin response to detecting the third input directed to the second user interface object, changing the appearance of the second user interface object from the third appearance to the second appearance.
23. The non-transitory computer-readable storage medium of claim 19, the one or more programs further including instructions for: while the first user interface object is displayed as being selected and while detecting the first input, detecting movement of the first input from a first position to a second position; andin response to detecting movement of the first input from the first position to the second position, moving display of the first user interface object based on the movement of the first input.
24. The non-transitory computer-readable storage medium of claim 19, wherein the first user interface object is displayed at a third position on the user interface prior to detecting the first input, the one or more programs further including instructions for: in response to detecting the first input, displaying a residual image of the first user interface object at the third position on the user interface.
25. The non-transitory computer-readable storage medium of claim 19, the one or more programs further including instructions for: while the first user interface object, the second user interface object, and the third user interface object are displayed as being selected and while detecting the first input, detecting liftoff of the first input; andin response to detecting liftoff of the first input, performing an action on the first user interface object, the second user interface object, and the third user interface object.
26. The non-transitory computer-readable storage medium of claim 19, the one or more programs further including instructions for: while the first user interface object is displayed as being selected, detecting an input that corresponds to selection of a fourth user interface object; andin response to detecting the input that corresponds to selection of the fourth user interface object, displaying the first user interface object and the fourth user interface object as being grouped together.
27. The non-transitory computer-readable storage medium of claim 19, wherein the first input is an input that is moved across the second user interface object and the third user interface object.

Priority Claims (1)

Number	Date	Country	Kind
PCT/US2009/057899	Sep 2009	WO	international

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/035,367, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Sep. 28, 2020, now U.S. Pat. No. 11,334,229, which is a continuation of U.S. patent application Ser. No. 16/791,257, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Feb. 14, 2020, now U.S. Pat. No. 10,788,965, which is a continuation of U.S. patent application Ser. No. 16/403,184, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed May 3, 2019, now U.S. Pat. No. 10,564,826, which is a continuation of U.S. patent application Ser. No. 15/088,450, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Apr. 1, 2016, now U.S. Pat. No. 10,282,070, which is a continuation of U.S. patent application Ser. No. 13/909,002, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Jun. 3, 2013, now U.S. Pat. No. 9,310,907, which is a continuation of U.S. patent application Ser. No. 12/567,570, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Sep. 25, 2009, now U.S. Pat. No. 8,456,431, which claims priority to International Application No. PCT/US09/57899, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Sep. 22, 2009, which are incorporated by reference herein in their entirety. This application is related to the following applications: (1) U.S. patent application Ser. No. 12/567,460, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Sep. 25, 2009; (2) U.S. patent application Ser. No. 12/567,553, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Sep. 25, 2009; and (3) U.S. patent application Ser. No. 12/567,570, “Device, Method, and Graphical User Interface for Manipulating User Interface Objects,” filed Sep. 25, 2009, which are incorporated by reference herein in their entirety.

US Referenced Citations (676)

Number	Name	Date	Kind
4885786	Anderson et al.	Dec 1989	A
5283561	Lumelsky et al.	Feb 1994	A
5327161	Logan et al.	Jul 1994	A
5359703	Robertson et al.	Oct 1994	A
5371845	Newell et al.	Dec 1994	A
5424756	Ho et al.	Jun 1995	A
5463725	Henckel et al.	Oct 1995	A
5483261	Yasutake	Jan 1996	A
5490241	Mallgren et al.	Feb 1996	A
5499334	Staab	Mar 1996	A
5511148	Wellner	Apr 1996	A
5533183	Henderson et al.	Jul 1996	A
5581670	Bier et al.	Dec 1996	A
5583542	Capps	Dec 1996	A
5602981	Hargrove	Feb 1997	A
5675753	Hansen et al.	Oct 1997	A
5677708	Matthews et al.	Oct 1997	A
5685723	Ladin et al.	Nov 1997	A
5712995	Cohn	Jan 1998	A
5729673	Cooper et al.	Mar 1998	A
5732227	Kuzunuki et al.	Mar 1998	A
5767835	Obbink et al.	Jun 1998	A
5808601	Leah et al.	Sep 1998	A
5825349	Meier et al.	Oct 1998	A
5825352	Bisset et al.	Oct 1998	A
5841435	Dauerer et al.	Nov 1998	A
5845122	Nielsen et al.	Dec 1998	A
5864868	Contois	Jan 1999	A
5872559	Shieh	Feb 1999	A
5880743	Moran et al.	Mar 1999	A
5886697	Naughton et al.	Mar 1999	A
5910800	Shields et al.	Jun 1999	A
5969283	Looney et al.	Oct 1999	A
6025844	Parsons	Feb 2000	A
6028271	Gillespie et al.	Feb 2000	A
6055543	Christensen et al.	Apr 2000	A
6065021	George	May 2000	A
6073036	Heikkinen et al.	Jun 2000	A
6075531	Destefano	Jun 2000	A
6088649	Kadaba et al.	Jul 2000	A
6118450	Proehl et al.	Sep 2000	A
6141007	Elterman et al.	Oct 2000	A
6154210	Anderson	Nov 2000	A
6160551	Naughton et al.	Dec 2000	A
6167469	Safai et al.	Dec 2000	A
6175364	Wong et al.	Jan 2001	B1
6208329	Ballare	Mar 2001	B1
6215490	Kaply	Apr 2001	B1
6232957	Hinckley	May 2001	B1
6237010	Hui et al.	May 2001	B1
6244988	Delman	Jun 2001	B1
6245982	Suzuki et al.	Jun 2001	B1
6248946	Dwek	Jun 2001	B1
6253218	Aoki et al.	Jun 2001	B1
6266057	Kuzunuki et al.	Jul 2001	B1
6278443	Amro et al.	Aug 2001	B1
6292273	Dow et al.	Sep 2001	B1
6301586	Yang et al.	Oct 2001	B1
6317784	Mackintosh et al.	Nov 2001	B1
6323846	Westerman et al.	Nov 2001	B1
6334025	Yamagami et al.	Dec 2001	B1
6346935	Nakajima et al.	Feb 2002	B1
6346951	Mastronardi	Feb 2002	B1
6356971	Katz et al.	Mar 2002	B1
6374177	Lee et al.	Apr 2002	B1
6380947	Stead	Apr 2002	B1
6392673	Andrew et al.	May 2002	B1
6462760	Cox et al.	Oct 2002	B1
6480813	Bloomquist et al.	Nov 2002	B1
6545669	Kinawi et al.	Apr 2003	B1
6564213	Ortega et al.	May 2003	B1
6565608	Fein et al.	May 2003	B1
6570557	Westerman et al.	May 2003	B1
6646655	Brandt et al.	Nov 2003	B1
6657615	Harada	Dec 2003	B2
6677932	Westerman	Jan 2004	B1
6686935	Richard	Feb 2004	B1
6690365	Hinckley et al.	Feb 2004	B2
6713312	Blalock et al.	Mar 2004	B2
6731312	Robbin	May 2004	B2
6784925	Tomat et al.	Aug 2004	B1
6807361	Girgensohn et al.	Oct 2004	B1
6856259	Sharp	Feb 2005	B1
6888536	Westerman et al.	May 2005	B2
6903751	Saund et al.	Jun 2005	B2
6920619	Milekic	Jul 2005	B1
6928619	Clow et al.	Aug 2005	B2
6950989	Rosenzweig et al.	Sep 2005	B2
7030861	Westerman et al.	Apr 2006	B1
7093192	Mullen et al.	Aug 2006	B2
7110005	Arvin et al.	Sep 2006	B2
7134093	Etgen et al.	Nov 2006	B2
7158158	Fleming et al.	Jan 2007	B1
7164410	Kupka	Jan 2007	B2
7190379	Nissen	Mar 2007	B2
7216293	Kataoka et al.	May 2007	B2
7218226	Wehrenberg	May 2007	B2
7287241	Balsiger	Oct 2007	B2
7380212	Cody et al.	May 2008	B2
7444390	Tadayon et al.	Oct 2008	B2
7453444	Geaghan	Nov 2008	B2
7454717	Hinckley et al.	Nov 2008	B2
7456823	Poupyrev et al.	Nov 2008	B2
7469381	Ording	Dec 2008	B2
7469833	Kelley et al.	Dec 2008	B1
7477233	Duncan et al.	Jan 2009	B2
7489324	Royal et al.	Feb 2009	B2
7555710	Kobashi et al.	Jun 2009	B2
7557797	Ludwig	Jul 2009	B2
7559034	Paperny et al.	Jul 2009	B1
7614008	Ording	Nov 2009	B2
7619618	Westerman et al.	Nov 2009	B2
7627828	Collison et al.	Dec 2009	B1
7633076	Huppi et al.	Dec 2009	B2
7634725	Nishikawa	Dec 2009	B2
7653883	Hotelling et al.	Jan 2010	B2
7657849	Chaudhri et al.	Feb 2010	B2
7663607	Hotelling et al.	Feb 2010	B2
7688306	Wehrenberg et al.	Mar 2010	B2
7694231	Kocienda et al.	Apr 2010	B2
7695406	Waters	Apr 2010	B2
7705830	Westerman et al.	Apr 2010	B2
7728823	Lyon et al.	Jun 2010	B2
7743348	Robbins et al.	Jun 2010	B2
7779358	Gupta et al.	Aug 2010	B1
7791755	Mori	Sep 2010	B2
7812826	Ording et al.	Oct 2010	B2
7823080	Miyajima et al.	Oct 2010	B2
7856605	Ording et al.	Dec 2010	B2
7904810	Chen et al.	Mar 2011	B2
7934156	Forstall et al.	Apr 2011	B2
7936341	Weiss	May 2011	B2
7956847	Christie	Jun 2011	B2
7970240	Chao et al.	Jun 2011	B1
7996788	Carmichael	Aug 2011	B2
8023158	Maki et al.	Sep 2011	B2
8024658	Fagans et al.	Sep 2011	B1
8024667	Shaw et al.	Sep 2011	B2
8060229	Gupta et al.	Nov 2011	B2
8095884	Karunakaran et al.	Jan 2012	B2
8106856	Matas et al.	Jan 2012	B2
8132116	Schendel	Mar 2012	B1
8152640	Shirakawa et al.	Apr 2012	B2
8161400	Kwon	Apr 2012	B2
8171401	Sun	May 2012	B2
8171431	Grossman et al.	May 2012	B2
8176435	Jitkoff et al.	May 2012	B1
8176438	Zaman et al.	May 2012	B2
8209630	Thimbleby et al.	Jun 2012	B2
8259132	Buchheit	Sep 2012	B2
8276085	Sherwani	Sep 2012	B2
8291349	Park et al.	Oct 2012	B1
8291350	Park et al.	Oct 2012	B1
8305355	Forstall et al.	Nov 2012	B2
8312387	Williams et al.	Nov 2012	B2
8339420	Hiraoka et al.	Dec 2012	B2
8448083	Migos et al.	May 2013	B1
8451268	Reisman et al.	May 2013	B1
8456431	Victor	Jun 2013	B2
8458617	Victor et al.	Jun 2013	B2
8464173	Victor et al.	Jun 2013	B2
8487885	Relyea, Jr.	Jul 2013	B2
8525799	Grivna et al.	Sep 2013	B1
8539385	Capela et al.	Sep 2013	B2
8539386	Capela et al.	Sep 2013	B2
8612884	Capela et al.	Dec 2013	B2
8677268	Capela et al.	Mar 2014	B2
8766928	Weeldreyer et al.	Jul 2014	B2
8780069	Victor et al.	Jul 2014	B2
8799826	Missig et al.	Aug 2014	B2
8832585	Haggerty et al.	Sep 2014	B2
8863016	Victor et al.	Oct 2014	B2
8957865	Cieplinski et al.	Feb 2015	B2
8966399	Chiang et al.	Feb 2015	B2
8972879	Migos et al.	Mar 2015	B2
9081494	Migos et al.	Jul 2015	B2
9098182	Migos et al.	Aug 2015	B2
9310907	Victor et al.	Apr 2016	B2
9449365	Roberts	Sep 2016	B2
9459792	Matas et al.	Oct 2016	B2
9532734	Hoffman et al.	Jan 2017	B2
9880805	Guralnick	Jan 2018	B1
10220258	Gu et al.	Mar 2019	B2
10282070	Victor	May 2019	B2
10304347	Wilson et al.	May 2019	B2
10777314	Williams et al.	Sep 2020	B1
11103161	Williams et al.	Aug 2021	B2
11152100	Crowley et al.	Oct 2021	B2
11202598	Soli et al.	Dec 2021	B2
11209957	Dryer et al.	Dec 2021	B2
11317833	Williams et al.	May 2022	B2
11334229	Victor	May 2022	B2
11446548	Devine et al.	Sep 2022	B2
11452915	Devine et al.	Sep 2022	B2
20010014184	Bubie et al.	Aug 2001	A1
20020008763	Kawamura et al.	Jan 2002	A1
20020015024	Westerman et al.	Feb 2002	A1
20020018051	Singh	Feb 2002	A1
20020018075	Maulik et al.	Feb 2002	A1
20020021758	Chui et al.	Feb 2002	A1
20020045960	Phillips et al.	Apr 2002	A1
20020054233	Juen	May 2002	A1
20020057292	Holtz	May 2002	A1
20020057461	Dow et al.	May 2002	A1
20020062321	Shibata	May 2002	A1
20020070982	Hill et al.	Jun 2002	A1
20020086774	Warner	Jul 2002	A1
20020106199	Ikeda	Aug 2002	A1
20020109668	Rosenberg et al.	Aug 2002	A1
20020109708	Peurach et al.	Aug 2002	A1
20020135621	Angiulo et al.	Sep 2002	A1
20020161772	Bergelson et al.	Oct 2002	A1
20030014382	Iwamoto et al.	Jan 2003	A1
20030048291	Dieberger	Mar 2003	A1
20030064860	Yamashita et al.	Apr 2003	A1
20030081135	Boll	May 2003	A1
20030108241	Colmenarez et al.	Jun 2003	A1
20030122787	Zimmerman et al.	Jul 2003	A1
20030128192	Van Os	Jul 2003	A1
20030128241	Watanabe et al.	Jul 2003	A1
20030134714	Oishi et al.	Jul 2003	A1
20030142137	Brown et al.	Jul 2003	A1
20030149990	Anttila et al.	Aug 2003	A1
20030169288	Misawa	Sep 2003	A1
20030179240	Gest	Sep 2003	A1
20030189597	Anderson et al.	Oct 2003	A1
20030197687	Shetter	Oct 2003	A1
20030210268	Kataoka et al.	Nov 2003	A1
20030234768	Rekimoto et al.	Dec 2003	A1
20040046886	Ambiru et al.	Mar 2004	A1
20040066407	Regan et al.	Apr 2004	A1
20040088656	Washio	May 2004	A1
20040119758	Grossman et al.	Jun 2004	A1
20040135904	Shiota et al.	Jul 2004	A1
20040141009	Hinckley et al.	Jul 2004	A1
20040150668	Myers et al.	Aug 2004	A1
20040158555	Seedman et al.	Aug 2004	A1
20040174398	Luke et al.	Sep 2004	A1
20040174399	Wu et al.	Sep 2004	A1
20040183830	Cody et al.	Sep 2004	A1
20040205504	Phillips	Oct 2004	A1
20040207722	Koyama et al.	Oct 2004	A1
20040225968	Look et al.	Nov 2004	A1
20040239621	Numano et al.	Dec 2004	A1
20040239691	Sprang et al.	Dec 2004	A1
20050041035	Nagatomo et al.	Feb 2005	A1
20050052427	Wu et al.	Mar 2005	A1
20050062130	Ciancio et al.	Mar 2005	A1
20050068290	Jaeger	Mar 2005	A1
20050071767	Kirkland et al.	Mar 2005	A1
20050071774	Lipsky et al.	Mar 2005	A1
20050073601	Battles et al.	Apr 2005	A1
20050076307	Robbin	Apr 2005	A1
20050083406	Cozier	Apr 2005	A1
20050088418	Nguyen	Apr 2005	A1
20050088423	Keely et al.	Apr 2005	A1
20050091008	Green et al.	Apr 2005	A1
20050102635	Jiang et al.	May 2005	A1
20050104848	Yamaguchi et al.	May 2005	A1
20050108253	Metsatahti et al.	May 2005	A1
20050108620	Allyn et al.	May 2005	A1
20050108656	Wu et al.	May 2005	A1
20050134719	Beck	Jun 2005	A1
20050160377	Sciammarella et al.	Jul 2005	A1
20050177796	Takahashi	Aug 2005	A1
20050183026	Amano et al.	Aug 2005	A1
20050188329	Cutler et al.	Aug 2005	A1
20050195221	Berger et al.	Sep 2005	A1
20050198024	Sakata et al.	Sep 2005	A1
20050231512	Niles et al.	Oct 2005	A1
20050272564	Pyles et al.	Dec 2005	A1
20050289476	Tokkonen	Dec 2005	A1
20060001650	Robbins et al.	Jan 2006	A1
20060001652	Chiu et al.	Jan 2006	A1
20060004685	Pyhalammi et al.	Jan 2006	A1
20060017692	Wehrenberg et al.	Jan 2006	A1
20060022955	Kennedy	Feb 2006	A1
20060025218	Hotta	Feb 2006	A1
20060026521	Hotelling et al.	Feb 2006	A1
20060026535	Hotelling et al.	Feb 2006	A1
20060026536	Hotelling et al.	Feb 2006	A1
20060033721	Woolley et al.	Feb 2006	A1
20060033724	Chaudhri et al.	Feb 2006	A1
20060055662	Rimas-ribikauskas et al.	Mar 2006	A1
20060055684	Rimas-ribikauskas et al.	Mar 2006	A1
20060061663	Park	Mar 2006	A1
20060072028	Hong	Apr 2006	A1
20060077266	Nurmi et al.	Apr 2006	A1
20060080386	Roykkee et al.	Apr 2006	A1
20060085757	Andre et al.	Apr 2006	A1
20060085767	Hinckley et al.	Apr 2006	A1
20060088228	Marriott et al.	Apr 2006	A1
20060112335	Hofmeister et al.	May 2006	A1
20060125803	Westerman et al.	Jun 2006	A1
20060129945	Dettinger et al.	Jun 2006	A1
20060136246	Tu	Jun 2006	A1
20060136833	Dettinger et al.	Jun 2006	A1
20060136839	Makela et al.	Jun 2006	A1
20060161870	Hotelling et al.	Jul 2006	A1
20060164535	Oyama	Jul 2006	A1
20060170669	Walker et al.	Aug 2006	A1
20060174568	Kinoshita et al.	Aug 2006	A1
20060184966	Hunleth et al.	Aug 2006	A1
20060190833	Sangiovanni et al.	Aug 2006	A1
20060197750	Kerr et al.	Sep 2006	A1
20060197753	Hotelling	Sep 2006	A1
20060238517	King et al.	Oct 2006	A1
20060238521	Westerman et al.	Oct 2006	A1
20060240959	Huang	Oct 2006	A1
20060248469	Czerwinski et al.	Nov 2006	A1
20060279532	Olszewski et al.	Dec 2006	A1
20070016868	Nurmi	Jan 2007	A1
20070031115	Oshikiri et al.	Feb 2007	A1
20070033069	Rao et al.	Feb 2007	A1
20070050726	Wakai et al.	Mar 2007	A1
20070055940	Moore et al.	Mar 2007	A1
20070061748	Hirose	Mar 2007	A1
20070064004	Bonner et al.	Mar 2007	A1
20070067711	Woodall et al.	Mar 2007	A1
20070071256	Ito	Mar 2007	A1
20070079236	Schrier et al.	Apr 2007	A1
20070081740	Ciudad et al.	Apr 2007	A1
20070097421	Sorensen et al.	May 2007	A1
20070113198	Robertson et al.	May 2007	A1
20070113726	Oliver et al.	May 2007	A1
20070126732	Robertson et al.	Jun 2007	A1
20070136778	Birger et al.	Jun 2007	A1
20070150810	Katz et al.	Jun 2007	A1
20070150839	Danninger	Jun 2007	A1
20070152980	Kocienda et al.	Jul 2007	A1
20070152984	Ording et al.	Jul 2007	A1
20070160345	Sakai et al.	Jul 2007	A1
20070169614	Sasaki et al.	Jul 2007	A1
20070177803	Elias et al.	Aug 2007	A1
20070179938	Ikeda et al.	Aug 2007	A1
20070186154	Anthony et al.	Aug 2007	A1
20070186178	Schiller	Aug 2007	A1
20070188518	Vale et al.	Aug 2007	A1
20070192741	Yoritate et al.	Aug 2007	A1
20070192744	Reponen	Aug 2007	A1
20070192749	Baudisch	Aug 2007	A1
20070198942	Morris	Aug 2007	A1
20070204225	Berkowitz et al.	Aug 2007	A1
20070209004	Layard	Sep 2007	A1
20070220444	Sunday et al.	Sep 2007	A1
20070229471	Kim	Oct 2007	A1
20070229678	Barrus et al.	Oct 2007	A1
20070236475	Wherry	Oct 2007	A1
20070245236	Lee et al.	Oct 2007	A1
20070245257	Chan et al.	Oct 2007	A1
20070247435	Benko et al.	Oct 2007	A1
20070253025	Terayoko	Nov 2007	A1
20070257890	Hotelling et al.	Nov 2007	A1
20070263025	Ohashi et al.	Nov 2007	A1
20080019591	Iwayama et al.	Jan 2008	A1
20080022197	Bargeron et al.	Jan 2008	A1
20080030456	Asadi et al.	Feb 2008	A1
20080034317	Fard et al.	Feb 2008	A1
20080036743	Westerman et al.	Feb 2008	A1
20080040668	Ala-rantala	Feb 2008	A1
20080042978	Perez-noguera	Feb 2008	A1
20080051919	Sakai et al.	Feb 2008	A1
20080052945	Matas et al.	Mar 2008	A1
20080057941	Scott et al.	Mar 2008	A1
20080059888	Dunko	Mar 2008	A1
20080066010	Brodersen et al.	Mar 2008	A1
20080066015	Blankenhorn	Mar 2008	A1
20080066016	Dowdy et al.	Mar 2008	A1
20080072173	Brunner et al.	Mar 2008	A1
20080094368	Ording et al.	Apr 2008	A1
20080094370	Ording et al.	Apr 2008	A1
20080096726	Riley et al.	Apr 2008	A1
20080098331	Novick et al.	Apr 2008	A1
20080100642	Betancourt et al.	May 2008	A1
20080109751	Fitzmaurice et al.	May 2008	A1
20080111766	Uchino et al.	May 2008	A1
20080133697	Stewart et al.	Jun 2008	A1
20080134070	Kobayashi et al.	Jun 2008	A1
20080136786	Lanfermann et al.	Jun 2008	A1
20080140868	Kalayjian et al.	Jun 2008	A1
20080141135	Mason et al.	Jun 2008	A1
20080147664	Fujiwara et al.	Jun 2008	A1
20080148181	Reyes et al.	Jun 2008	A1
20080150715	Tang et al.	Jun 2008	A1
20080155474	Duhig et al.	Jun 2008	A1
20080155478	Stross	Jun 2008	A1
20080161161	Pipinich et al.	Jul 2008	A1
20080165141	Christie	Jul 2008	A1
20080165142	Kocienda et al.	Jul 2008	A1
20080167834	Herz et al.	Jul 2008	A1
20080168403	Westerman et al.	Jul 2008	A1
20080168404	Ording	Jul 2008	A1
20080174570	Jobs et al.	Jul 2008	A1
20080180404	Han et al.	Jul 2008	A1
20080180405	Han et al.	Jul 2008	A1
20080180406	Han et al.	Jul 2008	A1
20080186285	Shimizu	Aug 2008	A1
20080211766	Westerman et al.	Sep 2008	A1
20080216022	Lorch et al.	Sep 2008	A1
20080229223	Kake	Sep 2008	A1
20080244410	Schormann	Oct 2008	A1
20080259040	Ording et al.	Oct 2008	A1
20080262946	Wren	Oct 2008	A1
20080267468	Geiger et al.	Oct 2008	A1
20080270886	Gossweiler et al.	Oct 2008	A1
20080278455	Atkins et al.	Nov 2008	A1
20080284799	Hollemans et al.	Nov 2008	A1
20080297482	Weiss	Dec 2008	A1
20080303786	Nakamura et al.	Dec 2008	A1
20080307343	Robert	Dec 2008	A1
20080309632	Westerman et al.	Dec 2008	A1
20080320391	Lemay et al.	Dec 2008	A1
20080320419	Matas et al.	Dec 2008	A1
20090013350	Ohlfs et al.	Jan 2009	A1
20090021576	Linder et al.	Jan 2009	A1
20090037605	Li	Feb 2009	A1
20090051660	Feland et al.	Feb 2009	A1
20090051946	Hibi	Feb 2009	A1
20090052751	Chaney et al.	Feb 2009	A1
20090055748	Dieberger et al.	Feb 2009	A1
20090058821	Chaudhri	Mar 2009	A1
20090075782	Joubert et al.	Mar 2009	A1
20090079700	Abernathy	Mar 2009	A1
20090083655	Beharie et al.	Mar 2009	A1
20090100383	Sunday et al.	Apr 2009	A1
20090113330	Garrison et al.	Apr 2009	A1
20090122018	Vymenets et al.	May 2009	A1
20090128516	Rimon et al.	May 2009	A1
20090140997	Jeong et al.	Jun 2009	A1
20090150775	Miyazaki et al.	Jun 2009	A1
20090158326	Hunt et al.	Jun 2009	A1
20090164936	Kawaguchi	Jun 2009	A1
20090172606	Dunn et al.	Jul 2009	A1
20090174679	Westerman	Jul 2009	A1
20090178008	Herz et al.	Jul 2009	A1
20090183930	Yang et al.	Jul 2009	A1
20090184939	Wohlstadter et al.	Jul 2009	A1
20090193351	Lee et al.	Jul 2009	A1
20090228792	Van Os et al.	Sep 2009	A1
20090231275	Odgers	Sep 2009	A1
20090237363	Levy et al.	Sep 2009	A1
20090239587	Negron et al.	Sep 2009	A1
20090256809	Minor	Oct 2009	A1
20090256857	Davidson et al.	Oct 2009	A1
20090259964	Davidson et al.	Oct 2009	A1
20090259967	Davidson et al.	Oct 2009	A1
20090268949	Ueshima et al.	Oct 2009	A1
20090282332	Porat	Nov 2009	A1
20090282359	Saul et al.	Nov 2009	A1
20090303231	Robinet et al.	Dec 2009	A1
20090307589	Inose et al.	Dec 2009	A1
20090309881	Zhao et al.	Dec 2009	A1
20090327975	Stedman	Dec 2009	A1
20100002002	Lipsky et al.	Jan 2010	A1
20100004030	Nam et al.	Jan 2010	A1
20100007623	Kaneko et al.	Jan 2010	A1
20100017734	Cummins et al.	Jan 2010	A1
20100026647	Abe et al.	Feb 2010	A1
20100031202	Morris et al.	Feb 2010	A1
20100031203	Morris et al.	Feb 2010	A1
20100039399	Kim	Feb 2010	A1
20100050076	Roth	Feb 2010	A1
20100053111	Karlsson	Mar 2010	A1
20100058238	Ben Moshe	Mar 2010	A1
20100060586	Pisula et al.	Mar 2010	A1
20100062818	Haughay et al.	Mar 2010	A1
20100073318	Hu et al.	Mar 2010	A1
20100088624	Bligh et al.	Apr 2010	A1
20100088641	Choi	Apr 2010	A1
20100088653	Yach	Apr 2010	A1
20100090971	Choi et al.	Apr 2010	A1
20100095205	Kinoshita	Apr 2010	A1
20100095206	Kim	Apr 2010	A1
20100107101	Shaw et al.	Apr 2010	A1
20100134425	Storrusten	Jun 2010	A1
20100146436	Jakobson et al.	Jun 2010	A1
20100149211	Tossing et al.	Jun 2010	A1
20100153833	Siegel et al.	Jun 2010	A1
20100156813	Duarte et al.	Jun 2010	A1
20100162105	Beebe et al.	Jun 2010	A1
20100169819	Bestle et al.	Jul 2010	A1
20100184564	Molyneux et al.	Jul 2010	A1
20100185949	Jaeger	Jul 2010	A1
20100191701	Beyda et al.	Jul 2010	A1
20100194703	Fedor et al.	Aug 2010	A1
20100211920	Westerman et al.	Aug 2010	A1
20100214442	Uemura et al.	Aug 2010	A1
20100214571	Luo	Aug 2010	A1
20100218100	Simon et al.	Aug 2010	A1
20100228746	Harada	Sep 2010	A1
20100231533	Chaudhri	Sep 2010	A1
20100235794	Ording	Sep 2010	A1
20100241955	Price et al.	Sep 2010	A1
20100241994	Wiley	Sep 2010	A1
20100253807	Matsumoto et al.	Oct 2010	A1
20100262634	Wang	Oct 2010	A1
20100283743	Coddington	Nov 2010	A1
20100283750	Kang et al.	Nov 2010	A1
20100283754	Nakao et al.	Nov 2010	A1
20100289760	Jonoshita et al.	Nov 2010	A1
20100299598	Shin et al.	Nov 2010	A1
20100302176	Nikula et al.	Dec 2010	A1
20100309140	Widgor et al.	Dec 2010	A1
20100313125	Fleizach et al.	Dec 2010	A1
20100313126	Jung et al.	Dec 2010	A1
20100318904	Hillis et al.	Dec 2010	A1
20100325529	Sun	Dec 2010	A1
20100331145	Lakovic et al.	Dec 2010	A1
20100333044	Kethireddy	Dec 2010	A1
20110004830	Von Kaenel et al.	Jan 2011	A1
20110010672	Hope	Jan 2011	A1
20110012848	Li et al.	Jan 2011	A1
20110012856	Maxwell et al.	Jan 2011	A1
20110016120	Haughay et al.	Jan 2011	A1
20110018821	Kii et al.	Jan 2011	A1
20110029927	Lietzke et al.	Feb 2011	A1
20110029934	Locker et al.	Feb 2011	A1
20110055742	Tomono	Mar 2011	A1
20110069016	Victor	Mar 2011	A1
20110069017	Victor	Mar 2011	A1
20110069018	Atkins et al.	Mar 2011	A1
20110074710	Weeldreyer et al.	Mar 2011	A1
20110093812	Fong	Apr 2011	A1
20110093821	Wigdor et al.	Apr 2011	A1
20110099299	Vasudevan et al.	Apr 2011	A1
20110109581	Ozawa et al.	May 2011	A1
20110128367	Yoshioka et al.	Jun 2011	A1
20110145759	Leffert et al.	Jun 2011	A1
20110163944	Bilbrey et al.	Jul 2011	A1
20110163968	Hogan	Jul 2011	A1
20110179097	Ala-rantala	Jul 2011	A1
20110179368	King et al.	Jul 2011	A1
20110179373	Moore et al.	Jul 2011	A1
20110185316	Reid et al.	Jul 2011	A1
20110185321	Capela et al.	Jul 2011	A1
20110209058	Hinckley et al.	Aug 2011	A1
20110209100	Hinckley et al.	Aug 2011	A1
20110209102	Hinckley et al.	Aug 2011	A1
20110209104	Hinckley et al.	Aug 2011	A1
20110231796	Vigil	Sep 2011	A1
20110246918	Henderson	Oct 2011	A1
20110252370	Chaudhri	Oct 2011	A1
20110252380	Chaudhri	Oct 2011	A1
20110252381	Chaudhri	Oct 2011	A1
20110258537	Rives et al.	Oct 2011	A1
20110302519	Fleizach et al.	Dec 2011	A1
20110314422	Cameron et al.	Dec 2011	A1
20120015779	Powch et al.	Jan 2012	A1
20120023453	Wagner	Jan 2012	A1
20120023459	Westerman	Jan 2012	A1
20120026100	Migos et al.	Feb 2012	A1
20120030568	Migos et al.	Feb 2012	A1
20120030569	Migos et al.	Feb 2012	A1
20120036460	Cieplinski et al.	Feb 2012	A1
20120042272	Hong et al.	Feb 2012	A1
20120044150	Karpin et al.	Feb 2012	A1
20120116550	Hoffman et al.	May 2012	A1
20120117506	Koch et al.	May 2012	A1
20120166975	Oh et al.	Jun 2012	A1
20120188275	Shimazu et al.	Jul 2012	A1
20120251079	Meschter et al.	Oct 2012	A1
20120253485	Weast et al.	Oct 2012	A1
20130021368	Lee et al.	Jan 2013	A1
20130036380	Symons	Feb 2013	A1
20130061175	Matas et al.	Mar 2013	A1
20130174062	Stoustrup	Jul 2013	A1
20130179837	Eriksson et al.	Jul 2013	A1
20130198661	Matas	Aug 2013	A1
20130215064	Cholewin et al.	Aug 2013	A1
20130239049	Perrodin et al.	Sep 2013	A1
20130263055	Victor	Oct 2013	A1
20130263719	Watterson et al.	Oct 2013	A1
20130324210	Doig et al.	Dec 2013	A1
20140002387	Hashiba et al.	Jan 2014	A1
20140038781	Foley et al.	Feb 2014	A1
20140067096	Aibara	Mar 2014	A1
20140074825	Wood et al.	Mar 2014	A1
20140075373	Jitkoff et al.	Mar 2014	A1
20140075374	Jitkoff et al.	Mar 2014	A1
20140092291	Aoshima et al.	Apr 2014	A1
20140165000	Fleizach et al.	Jun 2014	A1
20140195918	Friedlander	Jul 2014	A1
20140213415	Parker et al.	Jul 2014	A1
20140225925	Hayashi et al.	Aug 2014	A1
20140282011	Dellinger et al.	Sep 2014	A1
20140282262	Gregotski et al.	Sep 2014	A1
20140333551	Kim et al.	Nov 2014	A1
20140344693	Reese et al.	Nov 2014	A1
20140351707	Haggerty et al.	Nov 2014	A1
20140358473	Goel et al.	Dec 2014	A1
20140371887	Hoffman et al.	Dec 2014	A1
20140372898	Ayres et al.	Dec 2014	A1
20150004578	Gilley et al.	Jan 2015	A1
20150007099	Koon et al.	Jan 2015	A1
20150015502	Al-nasser	Jan 2015	A1
20150039616	Rolston et al.	Feb 2015	A1
20150046814	Haughay et al.	Feb 2015	A1
20150111558	Yang	Apr 2015	A1
20150112700	Sublett et al.	Apr 2015	A1
20150113553	Pan	Apr 2015	A1
20150118657	Shrake et al.	Apr 2015	A1
20150130719	Wehrenberg et al.	May 2015	A1
20150133748	Edmonds et al.	May 2015	A1
20150177979	Johansson et al.	Jun 2015	A1
20150181314	Swanson	Jun 2015	A1
20150185967	Ly et al.	Jul 2015	A1
20150196804	Koduri et al.	Jul 2015	A1
20150199494	Koduri et al.	Jul 2015	A1
20150251053	Hoffman et al.	Sep 2015	A1
20150309692	Migos et al.	Oct 2015	A1
20150370323	Cieplinski et al.	Dec 2015	A1
20160048263	Hiraga et al.	Feb 2016	A1
20160058336	Blahnik et al.	Mar 2016	A1
20160107031	Palatsi et al.	Apr 2016	A1
20160110355	Charania et al.	Apr 2016	A1
20160216868	Victor et al.	Jul 2016	A1
20160255162	Frieder et al.	Sep 2016	A1
20160279475	Aragones et al.	Sep 2016	A1
20160283483	Jiang et al.	Sep 2016	A1
20160321831	Nakamura et al.	Nov 2016	A1
20170001073	Krueger et al.	Jan 2017	A1
20170019587	Matas et al.	Jan 2017	A1
20170053542	Wilson et al.	Feb 2017	A1
20170139554	Nakabayashi et al.	May 2017	A1
20170143262	Kurunmäki et al.	May 2017	A1
20170169295	Park et al.	Jun 2017	A1
20170192625	Kim et al.	Jul 2017	A1
20170209766	Riley et al.	Jul 2017	A1
20170266494	Crankson et al.	Sep 2017	A1
20170329933	Brust et al.	Nov 2017	A1
20170337033	Duyan et al.	Nov 2017	A1
20170357382	Miura et al.	Dec 2017	A1
20180056132	Foley et al.	Mar 2018	A1
20180068019	Novikoff et al.	Mar 2018	A1
20180126248	Dion et al.	May 2018	A1
20180140903	Poure et al.	May 2018	A1
20180294053	Runyon et al.	Oct 2018	A1
20180318647	Foley et al.	Nov 2018	A1
20180329584	Williams et al.	Nov 2018	A1
20180339195	Bernotas	Nov 2018	A1
20180345078	Blahnik et al.	Dec 2018	A1
20180367862	Horii et al.	Dec 2018	A1
20190073081	Takahashi et al.	Mar 2019	A1
20190143194	Evancha et al.	May 2019	A1
20190155382	Ikuta et al.	May 2019	A1
20190184234	Packles et al.	Jun 2019	A1
20190209777	O'connell et al.	Jul 2019	A1
20190279520	Wilson et al.	Sep 2019	A1
20190313012	Matas	Oct 2019	A1
20190336827	Intonato et al.	Nov 2019	A1
20190339849	Williams et al.	Nov 2019	A1
20190339860	Chen et al.	Nov 2019	A1
20190342616	Domm et al.	Nov 2019	A1
20200004409	Victor	Jan 2020	A1
20200014967	Putnam	Jan 2020	A1
20200054931	Martin et al.	Feb 2020	A1
20200110814	Abuelsaad et al.	Apr 2020	A1
20200160961	Wadhawan et al.	May 2020	A1
20200225746	Bar-Zeev et al.	Jul 2020	A1
20200257434	Victor	Aug 2020	A1
20200356222	Clarke et al.	Nov 2020	A1
20200356590	Clarke et al.	Nov 2020	A1
20200379560	Krasadakis	Dec 2020	A1
20210093919	Lyke et al.	Apr 2021	A1
20210117072	Victor	Apr 2021	A1
20210243356	Matas et al.	Aug 2021	A1
20210252337	Devine et al.	Aug 2021	A1
20210252341	Devine et al.	Aug 2021	A1
20210252369	Devine et al.	Aug 2021	A1
20210255747	Devine et al.	Aug 2021	A1
20210255758	Devine et al.	Aug 2021	A1
20210255826	Devine et al.	Aug 2021	A1
20210379447	Lee	Dec 2021	A1
20220062707	Bedekar et al.	Mar 2022	A1
20220206647	Clarke et al.	Jun 2022	A1
20230014053	Devine et al.	Jan 2023	A1

Foreign Referenced Citations (133)

Number	Date	Country
1404233	Mar 2003	CN
1619541	May 2005	CN
1717918	Jan 2006	CN
1756273	Apr 2006	CN
101063925	Oct 2007	CN
101446884	Jun 2009	CN
101458586	Jun 2009	CN
101599002	Dec 2009	CN
101617288	Dec 2009	CN
104815428	Aug 2015	CN
107430483	Dec 2017	CN
0871177	Oct 1998	EP
1124175	Aug 2001	EP
1148412	Oct 2001	EP
1289210	Mar 2003	EP
1577746	Sep 2005	EP
1615114	Jan 2006	EP
1840717	Oct 2007	EP
2045703	Apr 2009	EP
2060970	May 2009	EP
2068237	Jun 2009	EP
2136290	Dec 2009	EP
2284675	Feb 2011	EP
2509074	Oct 2012	EP
3122038	Jan 2017	EP
2830093	Mar 2003	FR
2420260	May 2006	GB
3-217976	Sep 1991	JP
6-309138	Nov 1994	JP
7-175587	Jul 1995	JP
8-106469	Apr 1996	JP
10-93848	Apr 1998	JP
11-164175	Jun 1999	JP
11-168694	Jun 1999	JP
11-341425	Dec 1999	JP
2000-138883	May 2000	JP
2000-138888	May 2000	JP
2000-148591	May 2000	JP
2000-163031	Jun 2000	JP
2000-221879	Aug 2000	JP
2000-244673	Sep 2000	JP
2000-350134	Dec 2000	JP
2001-136303	May 2001	JP
2001-228971	Aug 2001	JP
2001-265481	Sep 2001	JP
2001-309019	Nov 2001	JP
2002-152559	May 2002	JP
2003-102868	Apr 2003	JP
2003-163820	Jun 2003	JP
2003-338975	Nov 2003	JP
2003-345491	Dec 2003	JP
2003-348432	Dec 2003	JP
2004-15586	Jan 2004	JP
2004-32346	Jan 2004	JP
2004-145291	May 2004	JP
2004-153832	May 2004	JP
2004-234661	Aug 2004	JP
2004-288208	Oct 2004	JP
2004-336536	Nov 2004	JP
2004-336711	Nov 2004	JP
2005-38101	Feb 2005	JP
2005-92386	Apr 2005	JP
2005-100084	Apr 2005	JP
2005-515530	May 2005	JP
2005-150836	Jun 2005	JP
2005-175991	Jun 2005	JP
2005-182320	Jul 2005	JP
2005-202483	Jul 2005	JP
2005-202651	Jul 2005	JP
2005-303728	Oct 2005	JP
2005-321516	Nov 2005	JP
2005-339420	Dec 2005	JP
2006-67344	Mar 2006	JP
2006-139340	Jun 2006	JP
2006-140865	Jun 2006	JP
2006-195592	Jul 2006	JP
2006-203809	Aug 2006	JP
2006-236249	Sep 2006	JP
2007-515775	Jun 2007	JP
2007-525775	Sep 2007	JP
2008-106469	May 2008	JP
2008-518330	May 2008	JP
2009-112731	May 2009	JP
2009-217815	Sep 2009	JP
2012-20134	Feb 2012	JP
2013-140171	Jul 2013	JP
2013-541061	Nov 2013	JP
2014-500740	Jan 2014	JP
5771242	Aug 2015	JP
2016-017331	Feb 2016	JP
2016-52512	Apr 2016	JP
2016-517329	Jun 2016	JP
2016-167299	Sep 2016	JP
2017-532069	Nov 2017	JP
2018-202174	Dec 2018	JP
2019-003670	Jan 2019	JP
10-2005-0051638	Jun 2005	KR
10-2005-0101162	Oct 2005	KR
10-2006-0032793	Apr 2006	KR
10-2009-0070491	Jul 2009	KR
10-2013-0026541	Mar 2013	KR
10-2016-0027943	Mar 2016	KR
10-2019-0022883	Mar 2019	KR
10-2019-0141702	Dec 2019	KR
199954807	Oct 1999	WO
200016186	Mar 2000	WO
200129702	Apr 2001	WO
2002080176	Oct 2002	WO
2003023593	Mar 2003	WO
2003081458	Oct 2003	WO
2005093550	Oct 2005	WO
2005103863	Nov 2005	WO
2005106800	Nov 2005	WO
2006020305	Feb 2006	WO
2006047697	May 2006	WO
2007098243	Aug 2007	WO
2008030779	Mar 2008	WO
2008044024	Apr 2008	WO
2008085737	Jul 2008	WO
2008138046	Nov 2008	WO
2009084141	Jul 2009	WO
2009084809	Jul 2009	WO
2009129402	Oct 2009	WO
2012015933	Feb 2012	WO
2012061438	May 2012	WO
2015179592	Nov 2015	WO
2016036582	Mar 2016	WO
2016160632	Oct 2016	WO
2018048510	Mar 2018	WO
2018213066	Nov 2018	WO
2019183422	Sep 2019	WO
2019217249	Nov 2019	WO
2019231982	Dec 2019	WO

Non-Patent Literature Citations (553)

Entry
US 2002/0018582 A1, 02/2002, Hagiwara et al. (withdrawn)
Advisory Action received for U.S. Appl. No. 10/497,076, mailed on Aug. 2, 2011, 3 pages.
Advisory Action received for U.S. Appl. No. 10/497,076, mailed on Oct. 28, 2008, 3 pages.
Advisory Action received for U.S. Appl. No. 12/848,087, mailed on Jun. 17, 2015, 3 pages.
Apple Inc. vs. Samsung Electronics Co. Ltd. et al., Judgment in Interlocutory proceeding, Case No. 396957/KG ZA 11-730, civil law sector, Aug. 24, 2011, pp. 1-65.
Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Motion To Supplement Invalidity Contentions, Case No. 11-cv-01846-LHK, filed Jan. 27, 2012 together with Exhibit 6, Jan. 27, 2012, 47 pages.
Apple Inc. vs. Samsung Electronics Co. Ltd., et al., Samsung's Patent Local Rule 3-3 and 3-4 Disclosures, Case No. 11-cv-01846-LHK, dated Oct. 7, 2011, together with Exhibits G-1 through G-7 and Exhibit H, Oct. 7, 2011, 287 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/584,783, mailed on May 4, 2020, 3 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 17/030,318, mailed on Jul. 30, 2021, 4 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 17/030,321, mailed on Jul. 30, 2021, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/450,531, mailed on Aug. 11, 2020, 5 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,776, mailed on May 13, 2020, 9 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,776, mailed on Nov. 25, 2020, 5 pages.
Brief Communication Relating to Oral Proceedings received for European Patent Application No. 11741385.6, mailed on Oct. 23, 2017, 17 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 12/566,994, mailed on Jan. 22, 2015, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 13/666,943, mailed on Aug. 11, 2016, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/281,524, mailed on Jun. 3, 2019, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/450,531, mailed on Nov. 12, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/450,531, mailed on Oct. 30, 2020, 2 pages.
Decision on Appeal received for U.S. Appl. No. 12/848,087, mailed on Aug. 29, 2018, 9 pages.
Decision to Grant received for European Patent Application No. 09756118.7, mailed on Jul. 13, 2017, 2 pages.
Decision to Grant received for European Patent Application No. 11178259.5, mailed on Apr. 4, 2019, 3 pages.
Decision to Grant received for European Patent Application No. 11702357.2, mailed on Jul. 14, 2016, 2 pages.
Decision to Grant received for European Patent Application No. 17180535.1, mailed on Feb. 4, 2021, 2 pages.
Decision to Refusal received for European Patent Application No. 11741385.6, mailed on Dec. 14, 2017, 23 pages.
European Search Report received for the European Patent Application No. 10172417.7, mailed on Jan. 7, 2011, 4 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/584,783, mailed on Feb. 17, 2021, 9 pages.
Examiner's Pre-Review Report received for Japanese Patent Application No. 2018-138559, mailed on Jul. 29, 2020, 6 pages (3 pages of English Translation and 3 pages of Official).
Ex-Parte Quayle Action received for U.S. Appl. No. 12/567,570, mailed on Oct. 3, 2012, 6 pages.
Extended European Search Report received for European Patent Application No. 16177552.3, mailed on Sep. 30, 2016, 7 pages.
Extended European Search Report received for European Patent Application No. 18197554.1, mailed on Jun. 3, 2019, 11 pages.
Extended European Search Report received for European Patent Application No. 21159939.4, mailed on Sep. 28, 2021, 13 pages.
Extended European Search Report received for European Patent Application No. 17180535.1, mailed on Oct. 30, 2017, 9 pages.
Final Office Action received for U.S. Appl. No. 10/497,076 mailed on Feb. 10, 2012, 25 pages.
Final Office Action received for U.S. Appl. No. 10/497,076, mailed on Apr. 26, 2013, 30 pages.
Final Office Action received for U.S. Appl. No. 10/497,076, mailed on Feb. 2, 2011, 22 pages.
Final Office Action received for U.S. Appl. No. 10/497,076, mailed on Jun. 12, 2008, 31 pages.
Final Office Action received for U.S. Appl. No. 10/497,076, mailed on Oct. 6, 2009, 29 pages.
Final Office Action received for U.S. Appl. No. 15/281,524, mailed on Dec. 27, 2018, 6 pages.
Final Office Action received for U.S. Appl. No. 16/584,783, mailed on May 19, 2020, 19 pages.
Final Office Action received for U.S. Appl. No. 17/030,321, mailed on Apr. 2, 2021, 28 pages.
Final Office Action received for U.S. Appl. No. 14/455,303, mailed on Mar. 13, 2017, 33 pages.
Final Office Action received for U.S. Appl. No. 14/455,303, mailed on May 11, 2018, 30 pages.
HTC Europe Co. Ltd and Apple Inc. invalidity Claim dated Jul. 29, 2011, together with amended Particulars of Claim and amended Grounds of Invalidity, Jul. 29, 2011, 22 pages.
HTC Europe Co. Ltd and Apple Inc. Invalidity Claim No. HC 12 C 01465, together with annexes, dated Apr. 5, 2012, 12 pages.
Intention to Grant received for European Patent Application No. 09756118.7, mailed on Mar. 2, 2017, 8 pages.
Intention to Grant received for European Patent Application No. 11178259.5, mailed on Nov. 8, 2018, 16 pages.
Intention to Grant received for European Patent Application No. 17180535.1, mailed on Sep. 24, 2020, 7 pages.
International Preliminary Examination Report on Patentability received for PCT Patent Application No. PCT/US2002/000484, mailed on Aug. 4, 2003, 7 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2002/000484, mailed on Jul. 11, 2002, 1 page.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031442, mailed on Oct. 30, 2020, 28 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/031442, mailed on Aug. 25, 2020, 22 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/017736, mailed on Jun. 15, 2021, 14 pages.
“Microsoft Support Webcasts”, Windows Media Player 7: New features and Walk-through Transcript, Jul. 13, 2000, 7 pages.
Minutes of Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Nov. 2, 2018, 9 pages.
Motorola Mobility Opposition Grounds to Apple Inc. European Patent EP 2126678 dated Apr. 11, 2012, together with Exhibits E3, E4, and E5 re: CHT 2005, Apr. 2-7, 2005, Portland Oregon, USA, Apr. 2012, 53 pages.
Non-Final Office Action received for U. S. U.S. Appl. No. 14/455,303, mailed on Jul. 29, 2016, 27 pages.
Office Action received for U.S. Appl. No. 14/455,303, mailed on Oct. 18, 2017, 30 pages.
Office Action received for U.S. Appl. No. 09/757,000, mailed on Jan. 30, 2003, 11 pages.
Office Action received for U.S. Appl. No. 09/757,000, mailed on Jun. 19, 2003, 11 pages.
Office Action received for U.S. Appl. No. 10/497,076, mailed on Jan. 8, 2009, 29 pages.
Office Action received for U.S. Appl. No. 10/497,076, mailed on May 13, 2010, 24 pages.
Office Action received for U.S. Appl. No. 10/497,076, mailed on Oct. 3, 2012, 24 pages.
Office Action received for U.S. Appl. No. 10/497,076, mailed on Oct. 13, 2011, 24 pages.
Non-Final Office Action received for U.S. Appl. No. 10/497,076, mailed on Sep. 13, 2007, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 15/088,450, mailed on Jul. 23, 2018, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 15/281,524, mailed on Jun. 19, 2018, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 16/450,531, mailed on Jun. 10, 2020, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 16/584,776, mailed on Aug. 18, 2020, 36 pages.
Non-Final Office Action received for U.S. Appl. No. 16/584,776, mailed on Feb. 13, 2020, 31 pages.
Non-Final Office Action received for U.S. Appl. No. 16/584,783, mailed on Jan. 30, 2020, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,318, mailed on Apr. 2, 2021, 28 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,318, mailed on Dec. 3, 2020, 22 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,321, mailed on Dec. 15, 2020, 25 pages.
Non-Final Office Action received for U.S. Appl. No. 17/035,367, mailed on Jun. 11, 2021, 11 pages.
Notice of Acceptance received for Australian Patent Application No. 2015201028, mailed on Mar. 21, 2017, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2017201548, mailed on Sep. 3, 2018, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2018214074, mailed on Aug. 6, 2019, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2019264623, mailed on Jan. 4, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2015202218, mailed on Dec. 20, 2016, 3 pages.
Notice of Allowance received for Australian Patent Application No. 2015202218, mailed on Apr. 11, 2017, 4 pages.
Notice of Allowance received for Canadian Patent Application No. 2,935,875, mailed on May 3, 2017, 1 page.
Notice of Allowance received for Canadian Patent Application No. 2,984,527, mailed on Apr. 30, 2020, 1 page.
Notice of Allowance received for Chinese Patent Application No. 201180016102.7, mailed on Sep. 5, 2016, 4 pages (2 pages of English Translation and 2 pages of Official).
Notice of Allowance received for Japanese Patent Application No. 2014-259225, mailed on Feb. 27, 2017, 3 pages. (Official Only).
Notice of Allowance received for Japanese Patent Application No. 2015-129152, mailed on May 8, 2017, 3 pages (Official only).
Notice of Allowance received for Japanese Patent Application No. 2017-057997, mailed on Apr. 23, 2018, 4 pages (1 page of English Translation and 3 pages of Official).
Notice of Allowance received for Japanese Patent Application No. 2017-132229, mailed on Jun. 25, 2018, 4 pages (1 page of English Translation and 3 pages of Official).
Notice of Allowance received for U.S. Appl. No. 09/757,000, mailed on Dec. 5, 2003, 4 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,570, mailed on Dec. 19, 2012, 7 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,570, mailed on Mar. 27, 2013, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,087, mailed on Nov. 20, 2018, 9 pages.
Notice of Allowance received for U.S. Appl. No. 13/666,943, mailed on Jun. 2, 2016, 9 pages.
Notice of Allowance received for U.S. Appl. No. 14/793,574, mailed on Dec. 13, 2016, 20 pages.
Notice of Allowance received for U.S. Appl. No. 15/088,450, mailed on Dec. 13, 2018, 7 pages.
Notice of Allowance received for U.S. Appl. No. 15/281,524, mailed on Apr. 11, 2019, 7 pages.
Notice of Allowance received for U.S. Appl. No. 16/403,184, mailed on Oct. 11, 2019, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/450,531 mailed on Sep. 25, 2020, 7 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,776, mailed on Feb. 1, 2021, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/791,257, mailed on Jun. 12, 2020, 11 pages.
Notice of Allowance received for U.S. Appl. No. 17/035,367, mailed on Sep. 23, 2021, 7 pages.
Notice of Allowance received for U.S. Appl. No. 14/455,303, mailed on Nov. 21, 2018, 6 pages.
Office Action received for Australian Patent Application No. 2017201548, mailed on Feb. 26, 2018, 2 pages.
Office Action received for Australian Patent Application No. 2018214074, mailed on May 9, 2019, 2 pages.
Office Action received for Australian Patent Application No. 2019264623, mailed on Sep. 14, 2020, 3 pages.
Office Action received for Australian Patent Application No. 2020239743, mailed on Mar. 25, 2021, 8 pages.
Office Action received for Australian Patent Application No. 2020239743, mailed on Sep. 3, 2021, 4 pages.
Office Action received for Australian Patent Application No. 2020239748, mailed on Apr. 21, 2021, 6 pages.
Office Action received for Australian Patent Application No. 2020239748, mailed on Sep. 1, 2021, 4 pages.
Office Action received for Australian Patent Application No. 2020239752, mailed on Jun. 4, 2021, 8 pages.
Office Action received for Canadian Patent Application No. 2,984,527 mailed on Sep. 11, 2018, 5 pages.
Office Action received for Canadian Patent Application No. 2,984,527, mailed on Jul. 25, 2019, 4 pages.
Office Action received for Danish Patent Application No. PA201970535, mailed on May 20, 2020, 3 pages.
Office Action received for Danish Patent Application No. PA201970535, mailed on Oct. 27, 2020, 6 pages.
Office Action received for European Patent Application No. 02713375.0, mailed on Feb. 27, 2009, 5 pages.
Office Action received for European Patent Application No. 11178259.5, mailed on Nov. 10, 2015, 4 pages.
Office Action received for European Patent Application No. 11702358.0, mailed on Jun. 28, 2016, 5 pages.
Office Action received for European Patent Application No. 11702358.0, mailed on Mar. 9, 2018, 4 pages.
Office Action received for European Patent Application No. 11741385.6, mailed on Sep. 27, 2016, 8 pages.
Office Action received for European Patent Application No. 16177552.3, mailed on Aug. 23, 2018, 7 pages.
Office Action received for European Patent Application No. 17180535.1, mailed on Oct. 8, 2018, 6 pages.
Office Action received for European Patent Application No. 17180535.1, mailed on Oct. 14, 2019, 8 pages.
Office Action received for European Patent Application No. 18197554.1, mailed on Jun. 15, 2020, 4 pages.
Office Action received for European Patent Application No. 02713375.0, mailed on Feb. 24, 2010, 4 pages.
Office Action received for Indian Patent Application No. 9044/CHENP/2014, mailed on Jan. 24, 2020, 6 pages.
Office Action received for Japanese Patent Application No. 2014-259225, mailed on May 27, 2016, 4 pages (2 pages of English Translation and 2 pages of Official).
Office Action received for Japanese Patent Application No. 2015-129152, mailed on Sep. 23, 2016, 3 pages (1 page of English Translation and 2 pages of Official).
Office Action received for Japanese Patent Application No. 2017-057997, mailed on Jan. 9, 2018, 6 pages (3 pages of English translation and 3 pages of official).
Office Action received for Japanese Patent Application No. 2017-132229, mailed on Mar. 16, 2018, 7 pages (3 pages of English Translation and 4 pages of Official).
Office Action received for Japanese Patent Application No. 2018-138559, mailed on Apr. 9, 2021, 30 pages (6 pages of English Translation and 24 pages of Official).
Office Action received for Japanese Patent Application No. 2018-138559, mailed on Jan. 27, 2020, 7 pages (3 pages of English Translation and 4 pages of Official).
Office Action received for Japanese Patent Application No. 2018-138559, mailed on Jul. 26, 2021, 37 pages (5 pages of English Translation and 32 pages of Official).
Office Action received for Japanese Patent Application No. 2018-138559, mailed on May 13, 2019, 10 pages (5 pages of English Translation and 5 pages of Official).
Office Action received for Japanese Patent Application No. 2020-079486, mailed on Jul. 16, 2021, 10 pages (5 pages of English Translation and 5 pages of Official).
Office Action received for European Patent Application No. 02713375.0, mailed on Feb. 24, 2014, 5 pages.
Partial European Search Report received for European Patent Application No. 18197554.1, mailed on Jan. 22, 2019, 8 pages.
Pleading notes Mr B.J. Berghuis van Woortman, in matter of Apple Inc. v. Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731, Aug. 10-11, 2010, pp. 1-16.
Pleading notes Mr Kleemans, Mr Blomme and Mr Van Oorschot, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731, Aug. 10, 2011, 35 pages.
Samsung Electronics GmbH v. Apple Inc., “List scrolling and document translation, scaling and rotation on a touch-screen display”, Opposition, Jan. 30, 2012, 27 pages.
Samsung Electronics v. Apple Inc., Statement of Defense Also Counterclaim, Case No. KG ZA 2011-730, Jul. 20, 2011, 44 pages.
Samsung Electronics v. Apple Inc., Statement of Defense Also Counterclaim, Case No. KG ZA 2011-731, Jul. 20, 2011, 48 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970535, mailed on Nov. 5, 2019, 10 pages.
Search Report and Opinion received for Danish Patent Application No. PA202070612, mailed on Jun. 7, 2021, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA202070613, mailed on Jan. 22, 2021, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA202070615, mailed on Jan. 22, 2021, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA202070616, mailed on Feb. 3, 2021, 8 pages.
“Spaces (software)”, Wikipedia, the free encyclopedia, available at <http://en.wikipedia.org/wiki/Spaces_(software)>, Jul. 15, 2009, 3 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 09756118.7, mailed on Sep. 23, 2016, 8 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Feb. 19, 2018, 12 pages.
Summons to attend Oral proceedings received for European Patent Application No. 11741385.6, mailed on Apr. 26, 2017, 10 pages.
Summons to Attend Oral proceedings received for European Patent Application No. 11741385.6, mailed on Oct. 19, 2017, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/403,184, mailed on Nov. 21, 2019, 3 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,776, mailed on Feb. 18, 2021, 3 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,776, mailed on May 13, 2021, 4 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/791,257, mailed on Aug. 31, 2020, 3 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/035,367, mailed on Oct. 27, 2021, 3 pages.
Supplementary European Search Report received for European Patent Application No. 02713375.0, mailed on Oct. 2, 2009, 3 pages.
Supplementary Search Report received for European Patent Application No. 02713375.0, mailed on Aug. 5, 2005, 3 pages.
“Support WebCast: Windows Media Player 7: New features and Walk-through”, Microsoft Knowledge Base Article-324594, Jul. 13, 2000, 2 pages.
“Virtual Desktop”, Wikipedia, the free encyclopedia, available at <http://en.wikipedia.org/wiki/Virtual_desktop>, Jul. 20, 2009, 5 pages.
“Visio 2003 Professional—Basics”, Available online at: URL: http://d.scribd.com/docs/2dolxjrcshr9fcemu941.pdf, retrieved on Mar. 15, 2009, pp. 77-80.
“WINAMP from Nullsoft”, screendumps of the media player having visual effect, version 2.62, 1997-2000, 2 pages.
“Windows Media Player Visualization”, To view a visualization, 2000-2001, 2 pages.
Decision to Grant received for the European Patent Application No. 07814633.9, mailed on Sep. 2, 2010, 3 pages.
Intention to Grant received for the European Patent Application No. 07814633.9, mailed on Mar. 19, 2010, 4 pages.
Office Action received for European Patent Application No. 07814633.9, mailed on Aug. 10, 2009, 3 pages.
Office Action received for European Patent Application No. 09756118.7, mailed on Feb. 13, 2013, 5 pages.
Office Action received for European Patent Application No. 09756118.7, mailed on Mar. 7, 2014, 7 pages.
Office Action Received for European Patent Application No. 09756118.7, mailed on Oct. 8, 2015, 6 pages.
Decision to Grant received for the European Patent Application No. 10172417.7, mailed on Nov. 14, 2013, 3 pages.
Intention to Grant received for European Patent Application No. 10172417.7, mailed on Jul. 9, 2013, 10 pages.
Office Action received for European Patent Application No. 10172417.7, mailed on Oct. 31, 2011, 6 pages.
Summons to Attend Oral Proceeding received for European Patent Application No. 10172417.7, Jan. 28, 2013, 6 pages.
Notice of Allowance received for Korean Patent Application No. 10-2012-7022209, mailed on Apr. 28, 2014, 5 pages (Official only).
Office Action received for Korean Patent Application No. 10-2012-7022209, mailed on Oct. 21, 2013, 4 pages (1 page English Translation 3 pages Official).
Notice of Allowance received for Korean Patent Application No. 10-2012-7022448, mailed on Apr. 27, 2015, 2 pages (Official only).
Office Action Received for Korean Patent Application No. 10-2012-7022448, mailed on Jun. 13, 2014, 3 pages (Official only).
Notice of Allowance received for Korean Patent Application No. 10-2013-7003785, mailed on Aug. 14, 2014, 2 pages (Official only).
Office Action received for Korean Patent Application No. 10-2013-7003785, mailed on Jan. 28, 2014, 4 pages (Official only).
Non-Final Office Action received for U.S. Appl. No. 11/848,210, mailed on Jun. 30, 2011, 8 pages.
Notice of Allowance received for U.S. Appl. No. 11/848,210, mailed on Dec. 20, 2011, 5 pages.
Decision to Grant received for the European Patent Application No. 11178257.9, mailed on Jun. 20, 2013, 3 pages.
Extended European Search Report received for European Patent Application No. 11178257.9, mailed on Oct. 31, 2011, 5 pages.
Intention to Grant received for European Patent Application No. 11178257.9, mailed on Jan. 30, 2013, 9 pages.
European Search Report received for the European Application No. 11178259.5, mailed on Oct. 31, 2011, 8 pages.
Office Action received for European Patent Application No. 11178259.5, mailed on Jan. 4, 2013, 8 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Feb. 11, 2015, 9 pages.
Intention to Grant received for European Patent Application No. 11702357.2, mailed on Feb. 26, 2016, 6 pages.
Office Action received for European Patent Application No. 11702357.2, mailed on Jan. 14, 2014, 5 pages.
Office Action received for European Patent Application No. 11741385.6, mailed on Jan. 22, 2014, 3 pages.
Office Action received for European Patent Application No. 11741385.6, mailed on Sep. 16, 2014, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 12/566,994, mailed on Dec. 13, 2013, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 12/566,994, mailed on Jan. 9, 2013, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 12/566,994, mailed on Jun. 13, 2014, 12 pages.
Notice of Allowance received for U.S. Appl. No. 12/566,994, mailed on May 22, 2013, 9 pages.
Notice of Allowance received for U.S. Appl. No. 12/566,994, mailed on Oct. 6, 2014, 8 pages.
Final Office Action received for U.S. Appl. No. 12/567,171, mailed on Jan. 3, 2013, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 12/567,171, mailed on Jul. 6, 2012, 13 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,171, mailed on Apr. 1, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,171, mailed on Oct. 4, 2013, 9 pages.
Final Office Action received for U.S. Appl. No. 12/567,206 mailed on Apr. 4, 2013, 21 pages.
Non-Final Office Action received for U.S. Appl. No. 12/567,206 mailed on Aug. 30, 2012, 13 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,206 mailed on May 8, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,206, mailed on Aug. 21, 2014, 6 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,206, mailed on Aug. 8, 2013, 8 pages.
Final Office Action received for U.S. Appl. No. 12/567,405, mailed on Dec. 17, 2012, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 12/567,405, mailed on Jan. 16, 2014, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 12/567,405, mailed on May 17, 2012, 14 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,405, mailed on Jun. 11, 2014, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/567,460, mailed on Aug. 4, 2011, 13 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Apr. 10, 2013, 9 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Aug. 10, 2012, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Dec. 24, 2012, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,460, mailed on Jan. 18, 2012, 8 pages.
Final Office Action received for U.S. Appl. No. 12/567,553, mailed on Mar. 12, 2012, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 12/567,553, mailed on Sep. 16, 2011, 11 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Apr. 2, 2013, 9 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Aug. 10, 2012, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Dec. 24, 2012, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/567,553, mailed on Jun. 12, 2012, 8 pages.
Final Office Action received for U.S. Appl. No. 12/768,623, mailed on Jan. 22, 2013, 34 pages.
Final Office Action received for U.S. Appl. No. 12/768,623, mailed on Oct. 23, 2013, 31 pages.
Non-Final Office Action received for U.S. Appl. No. 12/768,623, mailed on Jun. 7, 2012, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 12/768,623, mailed on May 30, 2013, 34 pages.
Notice of Allowance received for U.S. Appl. No. 12/768,623, mailed on Feb. 20, 2014, 8 pages.
Final Office Action received for U.S. Appl. No. 12/790,504, mailed on Apr. 1, 2013, 21 pages.
Non-Final Office Action received for U.S. Appl. No. 12/790,504, mailed on Oct. 3, 2012, 22 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,504, mailed on Aug. 13, 2013, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 12/790,508, mailed on Nov. 7, 2012, 32 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,508, mailed on Jul. 10, 2013, 7 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,508, mailed on Nov. 8, 2013, 11 pages.
Non-Final Office Action received for U.S. Appl. No. 12/790,516, mailed on Aug. 27, 2012, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 12/790,516, mailed on Feb. 2, 2012, 10 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,516, mailed on May 15, 2013, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 12/790,524, mailed on Sep. 24, 2012, 22 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,524, mailed on Feb. 5, 2013, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/790,524, mailed on May 13, 2013, 6 pages.
Final Office Action received for U.S. Appl. No. 12/848,063, mailed on Oct. 11, 2013, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,063, mailed on Aug. 9, 2012, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,063, mailed on Mar. 29, 2013, 13 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,063, mailed on Dec. 4, 2014, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,063, mailed on Mar. 27, 2015, 8 pages.
Final Office Action received for U.S. Appl. No. 12/848,067 mailed on Jan. 10, 2013, 35 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,067, mailed on Apr. 16, 2014, 40 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,067, mailed on Jun. 6, 2012, 16 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,067, mailed on Dec. 12, 2014, 2 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,067, mailed on Oct. 22, 2014, 23 pages.
Final Office Action received for U.S. Appl. No. 12/848,074, mailed on Apr. 3, 2013, Apr. 3, 2013, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,074, mailed on Jun. 29, 2012, 12 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on Apr. 28, 2015, 5 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on Jun. 3, 2015, 5 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on Mar. 13, 2015, 8 pages.
Notice of Allowance received for U.S. Appl. No. 12/848,074, mailed on May 13, 2014, 10 pages.
Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Jan. 28, 2015, 30 pages.
Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Aug. 22, 2013, 22 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Jul. 14, 2014, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 12/848,087, mailed on Mar. 7, 2013, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 12/849,767, mailed on Jul. 9, 2012, 16 pages.
Notice of Allowance received for U.S. Appl. No. 12/849,767, mailed on Jan. 8, 2013, 9 pages.
Notice of Allowance received for U.S. Appl. No. 12/849,767, mailed on Apr. 25, 2014, 5 pages.
Non-Final Office Action received for U.S. Appl. No. 13/361,912, mailed on Mar. 22, 2012, 8 pages.
Notice of Allowance received for U.S. Appl. No. 13/361,912, mailed on Jul. 2, 2012, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 13/666,943, mailed on Oct. 26, 2015, 12 Pages.
Notice of Allowance received for U.S. Appl. No. 13/666,943, mailed on Jun. 17, 2015, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 13/909,001, mailed on Sep. 26, 2013, 7 pages.
Notice of Allowance received for U.S. Appl. No. 13/909,001, mailed on Mar. 3, 2014, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 13/909,002, mailed on Jun. 23, 2015, 6 pages.
Notice of Allowance received for U.S. Appl. No. 13/909,002, mailed on Dec. 4, 2015, 7 pages.
Notice of Allowance received for the Canadian Patent Application No. 2,853,273, mailed on Jan. 12, 2016, 1 page.
Office Action received for Canadian Patent Application No. 2,853,273, mailed on Feb. 23, 2015, 5 pages.
Board Opinion received for Chinese Reexamination Patent Application No. 200780001142.8, mailed on Oct. 21, 2014, 13 pages (1 page of English Translation and 12 pages of Official).
Decision to Grant received for Japanese Patent Application No. 2009-526943, mailed on Dec. 2, 2011, Dec. 2, 2011, 3 pages (Official only).
Notice of Acceptance received for Australian Patent Application No. 2011209729, mailed on Jan. 15, 2015, 2 pages.
Office Action received for Australian Patent Application No. 2011209729, mailed on Jun. 24, 2013, Jun. 24, 2013, 4 pages.
Notice of Acceptance received for Australian Patent Application No. 2011265412, mailed on Nov. 12, 2014, 2 pages.
Notice of Acceptance received for Australian Patent Application No. 2011282703, mailed on May 8, 2015, 2 pages.
Office Action received for Australian Patent Application No. 2011282703, mailed on Oct. 21, 2013, 3 pages.
Office Action received for Chinese Patent Application No. 201180016102.7, mailed on Aug. 25, 2015, 23 pages (14 pages of English Translation and 9 pages of Official).
Office Action received for Chinese Patent Application No. 201180016102.7, mailed on Oct. 16, 2014, 10 pages (Official only).
Office Action received for Chinese Patent Application No. 2011800161027, mailed on Mar. 9, 2016, 8 pages (3 pages of English Translation and 5 pages of Official).
Notice of Allowance received for Chinese Patent Application No. 201180037474.8, mailed on Mar. 3, 2016, 3 pages (2 pages of English Translation and 1 page of official).
Office Action received for Chinese Patent Application No. 201180037474.8, mailed on Aug. 24, 2015, 8 pages (3 pages of English Translation and 5 pages of Official).
Office Action received for Chinese Patent Application No. 201180037474.8, mailed on Dec. 22, 2014, 6 pages (Official only).
Notice of Allowance received for Japanese Patent Application No. 2013-140171, mailed on May 29, 2015, 4 pages (Official only).
Office Action received for Japanese Patent Application No. 2013-140171, mailed on Jul. 22, 2014, 4 pages (2 pages of English Translation and 2 pages of Official).
Decision on Appeal received for Japanese Patent Application No. 2013521943, mailed on Mar. 25, 2016, Mar. 25, 2016, 3 pages (1 page of English Translation and 2 pages of official).
Office Action Received for Japanese Patent Application No. 2013521943, mailed on Nov. 2, 2015, 4 pages (2 pages of English Translation and 2 pages of Official).
Office Action received for Japanese Patent Application No. 2013-521943, mailed on Feb. 27, 2015, 2 pages (Official only).
Office Action received for Japanese Patent Application No. 2013-521943, mailed on Jan. 6, 2014, 2 pages (Official only).
Office Action received for Japanese Patent Application No. 2013-521943, mailed on Sep. 1, 2014, 2 pages (Official only).
Office Action Received for Japanese Patent Application No. 2014-259225, mailed on Nov. 20, 2015, 2 pages (Official Only).
Office Action received for Australian Patent Application No. 2015201028, issued on Mar. 15, 2016, 2 pages.
Office Action received for Australian Patent Application No. 2015202218, issued on Feb. 12, 2016, 5 pages.
Office action received for Indian Patent Application No. 2797CHENP2008 , mailed on Jan. 29, 2014, 3 pages.
Adeniyi Samuel, “How to connect a second PS4 controller to a PlayStation 4 console”, Online available on :- https://www.youtube.com/watch?v=mOZX_SINISE, May 28, 2017, 2 pages.
ALAI6666, “Jeff Han's 8 ft. Multi-Touch Display Wall”, Available online at <http://www.youtube.com/watch?v=JfFwgPuEdSk>, retrieved on May 16, 2007, 2 pages.
Alessandro Valli, “Minority Report interface prototype”, Available online at <http://www.youtube.com/watch?v=3bn-zZX9kdc>, retrieved on Jul. 12, 2006, 3 pages.
Allison Conor, “Working out with Fiit's wearable-powered boutique fitness classes”, Online available at:- <https://www.wareable.com/wearable-tech/fiit-fitness-classes-review-3849>, May 14, 2018, 8 pages.
Angell, “Is Bimanual the Future Paradigm for Human Computer Interaction?”, University of Plymouth, 2006, 2006, 36 pages.
Anthes Gary, “Give your computer the finger: Touch-screen tech comes of age”, Feb. 1, 2008, 3 Pages.
Apple.com, “Pages Keyboard Shortcuts”, available at <http://www.apple.com/support/pages/shortcuts/>, retrieved on Jan. 18, 2010, 6 pages.
Apted et al., “Tabletop Sharing of Digital Photographs for the Elderly”, CHI 2006: Proceedings, Apr. 2006, Montreal, Quebec, Canada, Apr. 2006, 10 pages.
Autodesklabs, “Autodesk Design on Jeff Han's Perceptive Pixel Multi-Touch”, Available online at <http://www.youtube.com/watch?v=O7ENumwMohs>, retrieved on Jul. 27, 2007, 2 pages.
Baudisch Patrick, “The Cage: Efficient Construction in 3D using a Cubic Adaptive Grid”, Proceedings of the 9th annual ACM symposium on User interface software and technology UIST '96, Nov. 6, 1996, 2 pages.
Beaudouin-Lafon et al., “CPN/Tools: A Post-WIMP Interface for Editing and Simulating Coloured Petri Nets”, Proceedings of 22nd International Conference on Application and Theory of Petri Nets 2001, 2001, pp. 1-10.
Beaudouin-Lafon M., “Novel Interaction Techniques for Overlapping Windows”, Available at <http://portal.acm.org/citation.cfm?id=502371>, 2001, pp. 153-154.
Bederson B., “PhotoMesa: A Zoomable Image Browser Using Quantum Treemaps and Bubblemaps”, UIST 2001, Oriando, Florida, Nov. 2001, 10 pages.
Benko et al., “Precise Selection Techniques for Multi-Touch Screens”, CHI 2006, Apr. 22-27, 2006, 10 pages.
Bestsheep1, “TDesktop Multiuser”, Available online on <http://www.youtube.com/watch?v=PjsO-Ibli34>, retrieved on Sep. 6, 2007, 2 pages.
Botjunkie, “Microsoft Surface Demo @ CES 2008”, Available online at <http://www.youtube.com/watch?v=Zxk_WywMTzc>, retrieved on Jan. 8, 2008, 2 pages.
Brandl et al., “Combining and Measuring the Benefits of Bimanual Pen and Direct-Touch Interaction on Horizontal Interfaces”, AVI'08, May 2008, Naples, Italy, May 2008, pp. 1-8.
Brandl P., “Combining and Measuring the Benefits of Bimanual Pen and Direct-Touch Interaction on Horizontal Interfaces”, Media Interaction Lab, Slide presentation, May 2008, 26 pages.
Brown Rich, “Touch mice: Smartphone-style input on your PC?”, Online available at :- https://www.cnet.com/news/touch-mice-smartphone-style-input-on-your-pc/, Feb. 15, 2012, 4 pages.
Bumptop, “3D Desktop”, Available online at <http://www.youtube.com/watch?v=I_IxBwvf3Vk>, retrieved on Sep. 18, 2006, Sep. 18, 2006, 2 pages.
Butz et al., “Hybrid Widgets on an Interactive Tabletop”, Ubicomp '07, Innsbruck, Austria, Sep. 2007, 7 pages.
Buxton Bill, “A Multi-Touch Three Dimensional Touch-Tablet”, Available online at <http://www.youtube.com/watch?v=Arrus9CxUiA>, retrieved on Nov. 18, 2009, 3 pages.
Buxton Bill, “Multi-Touch Systems that I Have Known and Loved”, available at <http://www.billbuxton.com/multitouchOverview.html>, Jan. 12, 2007, 14 pages.
Buxton et al., “A Study in Two-Handed Input”, Proceedings of CHI '86, Boston, MA, Apr. 1986, pp. 321-326.
Buxton W., “Chapter 11: Two-Handed Input in Human-Computer Interaction”, Aug. 22, 2008, pp. 11.1-11.18.
Buxton W., “Chapter 5: Case Study 1: Touch Tablets”, Haptic Input, Jan. 4, 2009, 20 pages.
Buxton et al., “Issues and Techniques in Touch-Sensitive Tablet Input”, Computer Graphics, vol. 19(3), http://http://www.dgp.toronto.edu/OTP/papers/bill.buxton/touch.html, Proceedings of SIGGRAPH'85, Jul. 22, 1985, pp. 215-224.
Buxton et al., “Multi-Touch Systems that I Have Known and Loved”, http://www.billbuxton.com/multitouchOverview.html, Jan. 12, 2007, pp. 1-21.
CBS This Morning, “This smart mirror puts a personal trainer in your reflection”, Available on: https://www.youtube.com/watch?v=nSmTTZcpVGg, Oct. 13, 2018, 4 pages.
Chanfrado, “Multi Touch (new touchscreen technology)”, Available online at <http://www.youtube.com/watch?v=1ftJhDBZqss>, retrieved on Mar. 17, 2006, 2 pages.
Chen et al., “Relative role of merging and two-handed operation on command selection speed”, Int. J. Human-Computer Studies 66 (2008), Jun. 2008, pp. 729-740.
Cho et al., “Interaction for Tabletop Computing Environment: An Analysis and Implementation”, Science And Technology (2005), ACM, 2005, pp. 11-18.
Cocoadex, “Photo Touch: Multi-touch Photo Organization for your Mac”, Available online at <http://www.youtube.com/watch?v=D7x7jV3P1-0>, retrieved on Mar. 30, 2008, 3 pages.
Continuumshow, “IdentityMine's Multitude of Multi-touch Apps”, Youtube, available online at <http://www.youtube.com/watch?v=HcpdNb9LHns>, Nov. 6, 2008, 2 pages.
Couturier et al., “Pointing Fingers: Using Multiple Direct Interactions with Visual Objects to Perform Music”, Proceedings of the 2003 Conference on New Interfaces for Musical Expression May 2003, Montreal, Canada, May 2003, pp. 184-187.
Cutedraw, “Moving, Rotating, Resizing and Flipping Shapes”, CuteDraw 2.0 Help System, available at: <http://www.cutedraw.com/Moving,%20Rotating,%20Resizing%20Flipping%20Shapes.php>, 2007, 5 pages.
Darthstoo, “Wii Multi-touch Photo Gallery”, Available online at <http://www.youtube.com/watch?v=0CYVxQ2OM9s>, retrieved on Apr. 10, 2008, 3 pages.
Derene G., “Microsoft Surface: Behind-the-Scenes First Look”, Popular Mechanics.com, Jul. 1, 2007 http://www.popularmechanics.com/technology/gadgets/news/4217348?page=3, Jul. 1, 2007, 4 pages.
Dwigdor, “Lucid Touch: a See-Through Multi-Touch Mobile Device”, Available online at <http://www.youtube.com/watch?v=qbMQ7urAvuc>, retrieved on Aug. 21, 2007, 2 pages.
Ed Bott, “Chapter 14. Playing and Recording Digital Music”, Special Edition Using Microsoft Windows Millennium Edition, Nov. 2000, pp. 329-353.
Engadget, “LG.Philips 52-inch multi-touch display”, Available online at <http://www.youtube.com/watch?v=9qO-diu4jq4>, retrieved on Jan. 8, 2008, 2 pages.
F0xmuld3r, “Multi-touch interface (from Adobe TED)”, Available online at <http://www.youtube.com/watch?v=UcKqyn-gUbY>, retrieved on Aug. 3, 2006, 2 pages.
Faas Ryan, “Spaces: A Look at Apple's Take on Virtual Desktops in Leopard”, Computerworld, available at <http://www.computerworld.com/s/article/9005267/Spaces_A_look_at_Apple_s_take_on_virtual_desktops_in_Leopard?taxonomyName...>, Nov. 21, 2006, 3 pages.
Fingerworks Forums, “Is the Multitouch Lemur?”, Available at <http://64233.167.104/search?q=cache:sjVdtyFBvRMJ:forums.finger>, retrieved on Nov. 16, 2005, Dec. 24, 2004, 2 pages.
Fingerworks, Inc., “Installation and Operation Guide for iGesture Products w/Keys”, available at <www.fingerworks.com>, © 2002, 10 pages.
Fingerworks, Inc., “Installation and Operation Guide for the TouchStream and TouchStream LP”, available at <http://www.fingerworks.com>, 2002, pp. 1-25.
Fingerworks, Inc., “Quick Reference Guide for iGesture Products”, available at <http://www.fingerworks.com>, 1999-2002, 2 pages.
Fingerworks, Inc., “Quick Reference Guide for TouchStream ST/LP”, available at <http://www.fingerworks.com>, 2001-2003, 4 pages.
Fingerworks, Inc., “TouchStream LP Silver”, available at <http://www.fingerworks.com>, Apr. 27, 2005, 18 pages.
Google Docs, “Drawings: Moving, resizing and rotating objects”, Downloaded from <https://support.google.com/docs/answer/141914?hl=-en> on Jan. 18, 2010, Jan. 18, 2010, 1 page.
Guimbretiere Francois, “Paper Augmented Digital Documents”, ACM, vol. 5, No. 2, 2003, pp. 51-60.
Guimbretière et al., “Benefits of Merging Command Selection and Direct Manipulation”, ACM Transactions on Computer-Human Interaction, vol. 12, No. 3, Sep. 2005, pp. 460-476.
Guimbretière F., “Curriculum Vitae (People, Paper and Computers)”, University of Maryland Institute for Advanced Computer Studies, 2008, 5 pages.
Hamilton Jim, “Peloton Tips”, Online available on :-<https://www.youtube.com/watch?app=desktop&v=OneXtB0kaD4>, Oct. 22, 2015, 3 pages.
Hcikonstanz, “Multi-touch Interaction: Browser Control”, Available online at <http://www.youtube.com/watch?v=jTOK5Zbfm4U>, retrieved on Sep. 12, 2008, 2 pages.
Helm Josh, “Microsoft® Windows Media™ Player Version 7—New features and Walk- through”, Jul. 2000, 20 pages.
Hinckley et al., “Interaction and Modeling Techniques for Desktop Two-Handed Input”, UIST '98, San Francisco, CA, Nov. 1998, 10 pages.
Hinckley et al., “Sensing Techniques for Mobile Interaction”, Symposium on User Interface Software and Technology, CHI Letters, vol. 2, No. 2, Nov. 2000, pp. 91-100.
Hinckley K., “Haptic Issues for Virtual Manipulation”, University of Virginia, Dissertation Presented, http://research.microsoft.com/en-us/um/people/kenh/all-published-papers/hinckley-thesis-haptic-issues-for-virtual-manipulation.pdf, Dec. 1996, 216 pages.
Hodges et al., “ThinSight: Versatile Multi-touch Sensing for Thin Form-factor Displays”, UIST '07, Newport, Rhode Island, USA, Oct. 7-10, 2007, 10 pages.
Hudson Scotte., “Adaptive Semantic Snaping—A Technique for Semantic Feedback at the Lexical Level”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1990, pp. 65-70.
13Pgroup, “I3 MultiTouch Interactive Table”, Youtube, available online at <http://www.youtube.com/watch?v=M2oijV-bRrw>, Nov. 16, 2007, 2 pages.
IBM, “Resizing Shapes by Dragging Sizing Handles”, IBM WebSphere Help System, available at <http://publib.boulder.ibm.com/infocenter/wsadhelp/v5r1m2/index.jsp?topic=/com.rational.xtools.umivisualizer.doc/topics/tresizedrag.html>, 1999, 1 page.
Inkspace, “Inkscape tutorial: Basic”, Inkscape.org, Apr. 20, 2005 http://web.archive.org/web20051225021958/http://inkscape.org/doc/basic/tutorial-basic.html, Apr. 20, 2005, pp. 1-7.
Intuilab, “Multitouch Time and Geo Tagging Photosharing with IntuiFace”, Available online at <http://www.youtube.com/watch?v=ftsx21liFvo>, retrieved on Jan. 31, 2008, Author name has been changed to “Multitouch.for Retail”, 3 pages.
Jin et al., “GIA: Design of a Gesture-Based Interaction Photo Album”, Pers Ubiquit Comput, Jul. 1, 2004, pp. 227-233.
Jobs Steve, “iPhone Introduction in 2007 (Complete)”, available at <https://www.youtube.com/watch?v=9hUIxyE2Ns8>, Jan. 10, 2013, 3 pages.
Kane et al., “Slide Rule: Making Mobile Touch Screens Accessible to Blind People Using Multi-Touch Interaction Techniques”, ASSETS, Oct. 15, 2008, pp. 73-80.
Karlson et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices”, CHI 2005, Papers: Small Devices 1, Apr. 2-7, 2005, pp. 201-210.
Karsenty et al., “Inferring Graphical Constraints with Rockit”, Digital-Paris Research Laboratory, Mar. 1992, 30 pages.
Korman Jonathan, “Intuition, pleasure, and gestures”, Available online at :-https://www.cooper.com/journal/2007/10/intuition_pleasure_and_gesture, Oct. 5, 2007, 4 pages.
Krishnaarava, “Cubit—Open Source Multitouch Display”, Available online at <http://www.youtube.com/watch?v=btFIrrDiUxk>, May 2, 2008, 3 pages.
Kristensson et al., “InfoTouch: An Explorative Multi-Touch Visualization Interface for Tagged Photo Collections”, Proceedings NordiCHI 2008, Oct. 20-22, 2008, pp. 491-494.
Kurata et al., “Tangible Tabletop Interface for an Expert to Collaborate with Remote Field Workers”, CollabTech2005, Jul. 16, 2005, Slides, 27 pages.
Kurata et al., “Tangible Tabletop Interface for an Expert to Collaborate with Remote Field Workers”, CollabTech2005, Jul. 16, 2005, pp. 58-63.
Kurtenbach et al., “The Design of A GUI Paradigm Based on Tablets, Two-Hands, and Transparency”, Mar. 27, 1997, 8 pages.
Kyocera WX300K, “Way to Use a Camera”, JP, Nov. 18, 2005, pp. 206-212. (Official Only).
Lee et al., “A Multi-Touch Three Dimensional Touch-Sensitive Tablet”, CHI '85 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1985, pp. 21-25.
Malik et al., “Visual Touchpad: A Two-Handed Gestural Input Device”, ICMI'04 Proceedings of the 6th International Conference on Multimodal Intercases, ACM, Oct. 13-15, 2004, pp. 289-296.
Markandtanya, “Imagining Multi-touch in Outlook”, May 2008, 3 pages.
Markusson D., “Interface Development of a Multi-Touch Photo Browser”, Umea University, Master's Thesis presented, Apr. 18, 2008, 76 pages.
Matsushita et al., “Dual Touch: A Two-Handed Interface for Pen-Based PDAs”, UIST '00, San Diego, California, Nov. 2000, 2 pages.
Matsushita et al., “HoloWall: Designing a Finger, Hand, Body and Object Sensitive Wall”, UIST '97 Proceedings of the 10th annual ACM symposium on User interface software and technology, Oct. 1997, 2 pages.
Media Interaction Lab, “Bimanual Pen & Touch”, http://mi-lab.org/projects/bimanual-pen-touch/, Nov. 2008, 5 pages.
Microsoft Windows, “Microsoft Windows (Copyright 2009)”, 2 pages.
Microsoft.com, “Quickly Formatting with the Format Painter”, available at <http://office.microsoft.com/enus/help/HA012176101033.aspx>, 2003, 1 page.
Microsoft.com, “Resize an Object”, Microsoft Office Online, available at <http://office.microsoft.com/en-us/publisher/HP051139751033.aspx>, 2010, 2 pages.
Moscovich et al., “Indirect Mappings of Multi-touch Input Using One and Two Hands”, CHI 2008, Florence, Italy, Apr. 2008, 9 pages.
Moscovich et al., “Multi-Finger Cursor Techniques”, GI '06 Proceedings of Graphics Interface 2006, Quebec City, Quebec, Canada, Jun. 9, 2006, 7 pages.
Moscovich T., “Multi-touch Interaction”, CHI 2006, Montreal, Quebec, Canada, Apr. 2006, pp. 1-4.
Moscovich T., “Principles and Applications of Multi-touch Interaction”, Brown University, Dissertation Presented, May 2007, 114 pages.
Mueller et al., “Visio 2007 for Dummies”, John Wiley & Sons, Dec. 18, 2006, pp. 178-181.
Murphy Peter, “Review: SBSH Calendar Touch”, available at <http://justanothermobilemonday.com/Wordpress/2008/12/08/review-sbsh-calendar-touch/>, Dec. 8, 2008, 7 pages.
Nepsihus, “PhotoApp (Multi-Touch)”, Available online at <http://www.youtube.com/watch?v=RJTVULGnZQ0>, retrieved on Dec. 30, 2007, 3 pages.
NextWindow, “NextWindow's Multi-Touch Overview”, v1.2, 2007, pp. 1-7.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/077441, issued on Mar. 10, 2009, 9 pages.
International Search Report and Written Opinion, received for PCT Patent Application No. PCT/US2007/077441, mailed on May 8, 2008, 13 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2007/077441, mailed on Jan. 28, 2008, 5 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2009/057899, mailed on Apr. 5, 2012, 14 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2009/057899, mailed on Jun. 14, 2010, 19 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2009/057899, mailed on Apr. 29, 2010, 8 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022519, mailed on Aug. 9, 2012, 8 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022519, mailed on Jul. 1, 2011, 8 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022525, mailed on Aug. 9, 2012, 8 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022525, mailed on Apr. 27, 2011, 10 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/022532, mailed on Aug. 9, 2012, 11 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/022532, mailed on May 24, 2011, 16 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/045552, issued on Feb. 5, 2013, 7 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/045552, mailed on Dec. 13, 2011, 10 pages.
Person et al., “Special Edition Using Windows 95”, Published by Que Corporation, 2nd Edition, 1997, pp. 335-337.
Raskin A., “Enso 2.0 Design Thoughts”, Aza's Thoughts, http://www.azarask.in/blog/post/enso-20-design-thoughts/, Dec. 6, 2008, 16 pages.
Raskin A., “Visual Feedback: Why Modes Kill”, Humanized, Dec. 2006, 18 pages.
Redmond Wash, “Microsoft Unveils Windows Media Player 7”, Microsoft Press Pass, Mar. 27, 2000, 4 pages.
Redmond Wash, “Worldwide Popularity of Microsoft Windows Media Player 7”, Microsoft PressPass, Aug. 2, 2000, 1 page.
Rubine Deanh., “The Automatic Recognition of Gestures”, CMU-CS-91-202, Thesis Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, Dec. 1991, 285 pages.
Sahlin et al., “Flash® CS4 All-in-One for Dummies®”, John Wiley & Sons, Dec. 3, 2008, 4 pages.
Sears et al., “High Precision Touchscreens: Design Strategies and Comparisons With a Mouse”, Human-Computer Interaction Laboratory, University of MD, Jan. 23, 1989, pp. 1-23.
Shen et al., “Informing the Design of Direct-Touch Tabletops”, IEEE Sep./Oct. 2006, Sep./Oct. 2006, pp. 36-46.
Shen C., “Interactive tabletops: User Interface, Metaphors and Gestures”, SIGGRAPH2007, Aug. 2007, 14 pages.
Skiljan Irfan, “IrfanView Help”, Irfan View Screen Dumps, 1996-1999, 3 pages.
Spadaccini, ““Multitouch Exhibit Design 1: Interaction and Feedback””, Available online at :- http://ideum.com/2009/02/25/multitouch-exhibit-design-1-interaction-and-feedback/, Feb. 25, 2009, 4 pages.
Tabletopresearch201, “Gesture Registration, Relaxation, and Reuse for Multi-Point”, Youtube, available online at <http://www.youtube.com/watch?v=dT4dXuah2yM>, May 19, 2008, 2 pages.
Thomas Gläser, “Photoshop MT—Desktop Digital Imaging on FTIR multitouch”, Available online at <http://www.youtube.com/watch?v=JmHNr9EH1iU>, retrieved on Feb. 7, 2007, 2 pages.
Thurrott Paul, ““Windows 8 Tip: Use Trackpad Multitouch Gestures””, Available online at :- http://winsupersite.com/windows-8/windows-8-tip-use-trackpad-multi-touch-gestures, Nov. 10, 2012, 5 pages.
Tse et al., “Enabling Interaction with Single User Applications Through Speech and Gestures on a Multi-User Tabletop”, Mitsubishi Electric Research Laboratories, 2005, pp. 336-343.
Ullmer et al., “The metaDESK: Models and Prototypes for Tangible User Interfaces”, UIST '97, Banff, Alberta, Canada, Oct. 14, 1997, pp. 1-10.
Unwirelife1, “HP TouchSmart tx2—Multi-Touch Part 2”, Youtube, available online at <http://www.youtube.com/watch?v=Yon3vRwc94A>, Dec. 19, 2008, 2 pages.
Vanderlin Todd, “Smart Surface Beta”, Available online at <http://www.youtube.com/watch?v=68wFqxdXENw>, retrieved on Mar. 29, 2008, 3 pages.
Vicky's Blog, “How to Log In to PS4 Automatically with Particular User?”, Online available on :- https://www.youtube.com/watch?v=kqdlzXAvOkY, May 30, 2018, 3 pages.
Westerman et al., “Multi-Touch: A New Tactile 2-D Gesture Interface for Human-Computer Interaction”, Proceedings of the Human Factors and Ergonomics Societ 45th Annual Meeting, 2001, pp. 632-636.
Westerman Wayne, “Hand Tracking, Finger Identification and Chordic Manipulation on A Multi-Touch Surface”, Doctoral Dissertation, 1999, 363 pages.
Willcom, “Operation Manual for WS003SH”, JP, Dec. 2005, pp. 4-1 to 4-7. (Official Only).
Wilson A., “Robust Computer Vision-Based Detection of Pinching for One and Two-Handed Gesture Input”, UIST '06, Montreux, Switzerland, Oct. 2006, 4 pages.
Wu et al., “Multi-Finger and Whole Hand Gestural Interaction Techniques for Multi-User Tabletop Displays”, UiST '03, Vancouver, BC, Canada, © ACM 2003, Nov. 5-7, 2003, pp. 193-202.
Yee Kap., “Two-Handed Interaction on a Tablet Display”, CHI 2004, Late Breaking Results Paper, Vienna, Austria, Apr. 24-29, 2004, pp. 1493-1496.
Yoyodavid, “How To Use Multiple Accounts on the Playstation 4”, Online available at :- https://www.youtube.com/watch?v=5V21obRMeKE, Jan. 9, 2014, 3 pages.
Zac96, “Microsoft Surface Demo”, Available online at <http://www.youtube.com/watch?v=rKgU6ubBgJA>, retrieved on Aug. 17, 2007, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Aug. 31, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/031,543, mailed on Aug. 22, 2022, 2 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/017736, mailed on Aug. 25, 2022, 19 pages.
Notice of Allowance received for Japanese Patent Application No. 2022-107902, mailed on Aug. 26, 2022, 4 pages (1 page of English Translation and 3 pages of Official).
Notice of Allowance received for Korean Patent Application No. 10-2020-0123815, mailed on Aug. 26, 2022, 7 pages (2 pages of English Translation and 5 pages of Official).
Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Aug. 22, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/153,703, mailed on Aug. 30, 2022, 8 pages.
Office Action received for European Patent Application No. 21159939.4, mailed on Sep. 2, 2022, 6 pages.
Office Action received for Korean Patent Application No. 10-2022-0061486, mailed on Aug. 29, 2022, 5 pages (2 pages of English Translation and 3 pages of Official).
Notice of Allowance received for U.S. Appl. No. 17/030,340, mailed on Sep. 28, 2022, 7 pages.
Office Action received for Indian Patent Application No. 202048019639, mailed on Sep. 27, 2022, 5 pages.
Office Action received for Korean Patent Application No. 10-2020-0123821, mailed on Sep. 20, 2022, 11 pages (5 pages of English Translation and 6 pages of Official).
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,343, mailed on Oct. 5, 2022, 2 pages.
Office Action received for European Patent Application No. 20729331.7, mailed on Jan. 4, 2023, 12 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,343, mailed on Jan. 6, 2023, 2 pages.
Notice of acceptance received for Australian Patent Application No. 2021202225, mailed on Jun. 20, 2022, 3 pages.
Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Dec. 23, 2022, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/153,703, mailed on Dec. 22, 2022, 7 pages.
Final Office Action received for U.S. Appl. No. 17/030,318, mailed on Nov. 28, 2022, 13 pages.
Notice of Allowance received for Korean Patent Application No. 10-2022-0061486, mailed on Nov. 22, 2022, 7 pages (2 pages of English Translation and 5 pages of Official).
Notice of Allowance received for U.S. Appl. No. 17/030,343, mailed on Dec. 15, 2022, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/697,539, mailed on Nov. 29, 2022, 10 pages.
Office Action received for Korean Patent Application No. 10-2020-0123840, mailed on Nov. 21, 2022, 18 pages (8 pages of English Translation and 10 pages of Official).
Updated Notice of Allowance received for U.S. Appl. No. 17/030,340, mailed on Dec. 2, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Sep. 21, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, mailed on Sep. 14, 2022, 2 pages.
Notice of Allowance received for U.S. Appl. No. 17/030,343, mailed on Sep. 16, 2022, 11 pages.
Office Action received for Chinese Patent Application No. 202111487316.4, mailed on Aug. 8, 2022, 25 pages (13 pages of English Translation and 12 pages of Official).
Office Action received for Danish Patent Application No. PA202070612, mailed on Sep. 12, 2022, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,321, mailed on Aug. 15, 2022, 3 pages.
Decision to Grant received for Danish Patent Application No. PA202070615, mailed on Jul. 29, 2022, 2 pages.
Office Action received for Japanese Patent Application No. 2020-160053, mailed on Aug. 1, 2022, 8 pages (4 pages of English Translation and 4 pages of Official).
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Oct. 18, 2022, 2 pages.
Notice of Allowance received for Japanese Patent Application No. 2020-079486, mailed on Oct. 21, 2022, 4 pages (1 page of English Translation and 3 pages of Official).
Office Action received for Danish Patent Application No. PA202070613, mailed on Oct. 13, 2022, 7 pages.
Updated Notice of Allowance received for U.S. Appl. No. 17/030,340, mailed on Nov. 2, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,543, mailed on Apr. 21, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/153,703, mailed on May 11, 2022, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Jan. 24, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/031,543, mailed on Jun. 8, 2022, 3 pages.
Decision on Appeal received for U.S. Appl. No. 16/584,783, mailed on Oct. 14, 2021, 12 pages.
Final Office Action received for U.S. Appl. No. 17/030,318, mailed on Sep. 30, 2021, 28 pages.
Intention to Grant received for Danish Patent Application No. PA202070615, maiied on Jan. 27, 2022, 2 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/031442, mailed on Nov. 18, 2021, 21 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/017736, mailed on Sep. 2, 2021, 25 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,337, mailed on Jun. 14, 2022, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,340, mailed on Jun. 14, 2022, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,318, mailed on Jun. 14, 2022, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 17/030,321, mailed on Oct. 18, 2021, 28 pages.
Non-Final Office Action received for U.S. Appl. No. 17/031,543, mailed on Apr. 1, 2022, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 17/153,703, mailed on Mar. 30, 2022, 10 pages.
Notice of Acceptance received for Australian Patent Application No. 2020239743, mailed on Jan. 13, 2022, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020239752, mailed on Jan. 31, 2022, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020267396, mailed on Dec. 7, 2021, 3 pages.
Notice of Allowance received for Australian Patent Application No. 2020239748, mailed on Mar. 7, 2022, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2018-138559, mailed on Dec. 3, 2021, 3 pages (1 page of English Translation and 2 pages of Official).
Notice of Allowance received for Japanese Patent Application No. 2020-160052, mailed on Jun. 3, 2022, 4 pages (1 page of English Translation and 3 pages of Official).
Notice of Allowance received for Japanese Patent Application No. 2020-160054, mailed on Apr. 4, 2022, 4 pages (1 page of English Translation and 3 pages of Official).
Notice of Allowance received for Korean Patent Application No. 10-2021-7036310, mailed on Apr. 26, 2022, 5 pages (2 pages of English Translation and 3 pages of Official).
Notice of Allowance received for U.S. Appl. No. 16/584,783, mailed on Dec. 20, 2021, 7 pages.
Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Jan. 5, 2022, 8 pages.
Notice of Allowance received for U.S. Appl. No. 17/030,321, mailed on Apr. 1, 2022, 8 pages.
Notice of Allowance received for U.S. Appl. No. 17/031,543, mailed on May 11, 2022, 6 pages.
Office Action received for Australian Patent Application No. 2020239748, mailed on Feb. 11, 2022, 2 pages.
Office Action received for Australian Patent Application No. 2020239752, mailed on Oct. 25, 2021, 5 pages.
Office Action received for Australian Patent Application No. 2021202225, mailed on Apr. 7, 2022, 3 pages.
Office Action received for Danish Patent Application No. PA 2020 70612, mailed on Mar. 1, 2022, 2 pages.
Office Action received for Danish Patent Application No. PA202070612, mailed on May 10, 2022, 2 pages.
Office Action received for Danish Patent Application No. PA202070613, mailed on May 10, 2022, 2 pages.
Office Action received for Danish Patent Application No. PA202070613, mailed on Sep. 30, 2021, 4 pages.
Office Action received for Danish Patent Application No. PA202070615, mailed on Nov. 16, 2021, 4 pages.
Office Action received for Danish Patent Application No. PA202070616, mailed on Jan. 27, 2022, 2 pages.
Office Action received for Danish Patent Application No. PA202070616, mailed on May 5, 2022, 3 pages.
Office Action received for German Patent Application No. 112007000067.8, mailed on Apr. 23, 2009, 15 pages (7 pages of English Translation and 8 pages of Official).
Office Action received for German Patent Application No. 112007000067.8, mailed on Sep. 14, 2010, 4 pages (2 pages of English Translation and 2 pages of Official).
Office Action received for Indian Patent Application No. 202014041563, mailed on Dec. 30, 2021, 6 pages.
Office Action received for Indian Patent Application No. 202014041571, mailed on Dec. 17, 2021, 5 pages.
Office Action received for Japanese Patent Application No. 2020-079486, mailed on Mar. 11, 2022, 8 pages (4 pages of English Translation and 4 pages of Official).
Office Action received for Japanese Patent Application No. 2020-160052, mailed on Dec. 17, 2021, 10 pages (5 pages of English Translation and 5 pages of Official).
Office Action received for Japanese Patent Application No. 2020-160053, mailed on Jan. 31, 2022, 8 pages (4 pages of English Translation and 4 pages of Official).
Office Action received for Japanese Patent Application No. 2020-160054, mailed on Jan. 21, 2022, 8 pages (4 pages of English Translation and 4 pages of Official).
Office Action received for Japanese Patent Application No. 2021-566100, mailed on May 27, 2022, 7 pages (3 pages of English Translation and 4 pages of Official).
Office Action received for Korean Patent Application No. 10-2020-0123815, mailed on May 31, 2022, 10 pages (5 pages of English Translation and 5 pages of Official).
Office Action received for Korean Patent Application No. 10-2021-7036310, mailed on Feb. 23, 2022, 6 pages (2 pages of English Translation and 4 pages of Official).
Summons to Attend Oral Proceedings received for European Patent Application No. 18197554.1, mailed on Mar. 23, 2022, 7 pages.
Summons to Oral Proceedings received for German Patent Application No. 112007000067.8, mailed on Dec. 8, 2021, 11 pages (5 pages of English Translation and 6 pages of Official).
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Apr. 4, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Feb. 22, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Mar. 16, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, mailed on Apr. 15, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, mailed on Jun. 10, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, mailed on May 27, 2022, 2 pages.
T&GG Channel, “Canon IXUS 700 / Screenshots of deleting an image”, Online available at: https://www.youtube.com/watch?v=8BL_L5hKZUM, May 2015, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Nov. 3, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Nov. 15, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, mailed on Nov. 10, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,343, mailed on Nov. 9, 2022, 2 pages.
Updated Notice of Allowance received for U.S. Appl. No. 17/030,340, mailed on Nov. 10, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/030,337, mailed on Jul. 27, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/031,543, mailed on Jul. 18, 2022, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/030,321, mailed on Jul. 27, 2022, 2 pages.
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18197554.1, mailed on Feb. 6, 2023, 8 pages.
Canon, “Camera User Guide Canon (UK) LTD”, Online available at: https://bedienungsanleitung-deutsch.de/bedienungsanleitung-handbuch/Canon_Digital_Ixus_700_EN.pdf, 2005, 196 pages.
“Canon IXUS 700—Additional Evidence and Information”, 2023, 3 pages (Official Only). {See Communication under 37 CFR § 1.98(a) (3)}.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Feb. 17, 2023, 2 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 18197554.1, mailed on Feb. 22, 2023, 9 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 17/697,539, mailed on Feb. 21, 2023, 2 pages.
Updated Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Feb. 23, 2023, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/030,337, mailed on Feb. 10, 2023, 2 pages.
Notice of Allowance received for Japanese Patent Application No. 2021-566100, mailed on Jan. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official).
Office Action received for Chinese Patent Application No. 202111487316.4, mailed on Dec. 28, 2022, 13 pages (8 pages of English Translation and 5 pages of Official).
Result of Consultation received for European Patent Application No. 18197554.1, mailed on Feb. 3, 2023, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-0123821, mailed on Mar. 28, 2023, 8 pages (2 pages of English Translation and 6 pages of Official).
Notice of Allowance received for Korean Patent Application No. 10-2023-0023706, mailed on Mar. 27, 2023, 8 pages (2 pages of English Translation and 6 pages of Official).
Decision to Refuse received for European Patent Application No. 18197554.1, mailed on Mar. 21, 2023, 17 pages.
Office Action received for Australian Patent Application No. 2022201810, mailed on Mar. 15, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, mailed on Jan. 19, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/697,539, mailed on Feb. 1, 2023, 2 pages.
Fono et al., “Eye Windows: Evaluation of Eye-Controlled Zooming Windows for Focus Selection”, CHI 2005, Conference Proceedings, Conference on Human Factors in Computing Systems, Apr. 2-7, 2005, pp. 151-160.
Notice of Allowance received for Japanese Patent Application No. 2020-160053, mailed on Jan. 16, 2023, 4 pages (1 page of English Translation and 3 pages of Official).
Notice of Allowance received for U.S. Appl. No. 17/030,318, mailed on Jan. 25, 2023, 10 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 21159939.4, mailed on May 23, 2023, 9 pages.

Related Publications (1)

	Number	Date	Country
	20220317846 A1	Oct 2022	US

Continuations (6)

	Number	Date	Country
Parent	17035367	Sep 2020	US
Child	17745021		US
Parent	16791257	Feb 2020	US
Child	17035367		US
Parent	16403184	May 2019	US
Child	16791257		US
Parent	15088450	Apr 2016	US
Child	16403184		US
Parent	13909002	Jun 2013	US
Child	15088450		US
Parent	12567570	Sep 2009	US
Child	13909002		US

Device, method, and graphical user interface for manipulating user interface objects

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Term Extension

Abstract