Patent Grant
9395888
In various embodiments, the present invention relates to application management in computing devices, and more particularly to systems and methods for implementing a card metaphor for activities such as software applications in such devices.
Many currently available computing devices run operating systems that offer users the opportunity to run several applications at the same time, and even to perform several activities simultaneously, within a single application and/or among two or more applications. For example, a user may open an e-mail application, a word processing application, an on-screen calculator, and a web browser, so that all of the applications are open concurrently. The user may open several documents within the word processing application, and may open several e-mail messages. Such an arrangement allows the user to move from one task to another by keeping these various applications and activities open at the same time.
Conventionally, such an operating paradigm is accomplished by the use of multiple overlapping windows within a graphical user interface. A desk-top metaphor is often employed, wherein the user can move and resize windows on a display screen by direct manipulation. Thus, each application may have a window or several windows; at any given time, one window has focus (usually indicated as such by being situated on top of the other windows). Other windows may be visible, invisible, or partially visible (for example if they are partially or completely obscured by other windows). A user can switch from one task to another by causing a different window to have focus; this is commonly accomplished by clicking on a visible portion of the window being activated, or by clicking on a button or icon representing the window or application in a task bar, quick-launch area, or similar construct. In some operating systems, pop-up menus and/or keyboard shortcuts may be available for switching among applications or documents.
Overlapping windows are a highly effective mechanism for application management. They exploit the user's spatial memory by associating a particular area of the screen with a particular task being performed. A user may find it easier to return to a previously opened window when he or she remembers that the window was placed at a particular location on the screen, as compared with a list or menu of open windows that does not provide a model of spatial placement and stability.
One issue with conventional window-based mechanisms for application management is that a large screen size is usually needed. Users faced with limited screen space must choose between, on the one hand, making windows smaller and thus reducing available workspace within each application, and, on the other hand, stacking windows atop each other so that only one window (or very few) is visible at a time. Reducing workspace can make it very difficult to use an application, particularly for applications such as word processing, photo editing, drawing, and the like. Stacking windows reduces the ease with which the user can switch from one application or document to another, as it is more difficult to see what is currently open and to find the appropriate window to be activated. When windows are stacked, users usually resort to navigation via taskbar, quick-launch area, menu, keyboard shortcut, or the like, thereby reducing the advantages of the overlapping window paradigm.
Some systems, such as the Mac OS operating system offered by Apple, Inc. of Cupertino, Calif., offer a mechanism for navigating among open applications by temporarily moving and shrinking open windows, moving the windows apart from one another so that they do not overlap. The user can then activate one of the windows; the original window positions and sizes are then restored, with the activated window on top. This feature is effective in allowing users to quickly switch among open applications and documents, but still requires a relatively large amount of screen space so as to effectively show the temporarily shrunk windows when the user is to select among them.
Mobile devices such as smartphones, personal digital assistants, music players, handheld computers, and the like are becoming increasingly powerful. Many are now able to run several applications concurrently, and to perform sophisticated functions that rival traditional computing devices. However, most such devices have extremely small screens, when compared to laptop or desk-top computers. Thus, the conventional window-based techniques for navigating among open applications and documents do not function very well on mobile devices. There is insufficient screen space to display multiple overlapping windows. In fact, many such devices do not even have enough space to display a task bar or quick-launch area. Rather, the entire screen is often devoted to a single application, document, message, task, or activity, so as to make the most effective use of the extremely limited amount of space available.
Related U.S. patent application Ser. No. 12/126,145, filed May 23, 2008, for “Navigating Among Activities in a Computing Device”, the disclosure of which is incorporated herein, describes various embodiments for running two or more activities concurrently on a computing device, and provides at least two modes for interacting with the activities. The user may toggle between the modes as desired. A button or other control is provided for switching between full-screen mode and card mode.
In various embodiments, a card metaphor is established, in which each activity can be represented within an area of the screen. For purposes of the description herein, these areas of the screen are referred to as “cards”. Although in some ways cards resemble windows as are known in the art of desk-top user interfaces, in various embodiments cards can be manipulated in particular ways that are not generally available to conventional window-based graphical user interfaces; such manipulations are described in more detail herein. One skilled in the art will recognize that the term “card” is used herein merely as a convenient term for referring to an area of the screen that contains information related to or generated by an activity such as a software application.
In various embodiments, any of several display modes are available for viewing, interacting with, manipulating, initiating, and dismissing cards.
In one embodiment, in a full-screen mode, one activity occupies substantially an entire display screen. The card thus fills substantially the entire display screen, although in some embodiments some areas of the screen may be reserved for status indicators, alerts, messages, and the like.
In one embodiment, a second mode is available, referred to as “card mode”. In card mode, one activity is visible within a card, and a portion of at least one other card is also visible. Thus, a card that has focus (i.e., that the user is interacting with) is visible in full, while at least one other card is only partially visible. In the card mode, the user can cause cards to move on the screen, so as to change focus from one card to another. For example, the card having focus can be moved off the screen, to be replaced by a new card that is then given focus. In one aspect, the cards are ordered in a sequence. In one aspect, the cards move in concert with one another; pushing one card off one edge of the screen causes a new card to appear at the opposite edge. A persistent positional relationship can be established among cards, based on the established sequence (although the user can rearrange the sequence if desired).
In one embodiment, a third mode is available, referred to as “shuffle mode”. In shuffle mode, two or more cards are shown in full. The size of the cards may be reduced so that more cards can be shown simultaneously. In addition, portions of one or more other cards may be visible. For example, in one embodiment, three cards can be shown in full in a horizontal row, with portions of two other cards shown to the left and right of the fully displayed cards. In one embodiment, shuffle mode facilitates easier reordering and manipulation of cards, and is associated with certain behaviors (described below) to optimize such operations. In one embodiment, shuffle mode resembles a zoomed out view of the cards presented in card view. In one embodiment, the user can zoom out to various degrees, so that several different varieties of shuffle mode can be presented, for example with different numbers of cards on the screen. In one embodiment, when more cards are displayed, they are displayed at a smaller size. In one embodiment, cards are presented in a linear arrangement in shuffle mode, preserving the linear sequence used in card mode.
In one embodiment, a fourth mode is available, referred to as “grid mode”. In grid mode, a larger number of cards are shown in full. In one embodiment, cards are scaled down in size so that all available cards are displayed simultaneously. In another embodiment, all cards are displayed to a predetermined maximum number of cards; if more than the predetermined maximum are available for display, scrolling is implemented to allow access to non-displayed cards. In one embodiment, cards are presented in a grid arrangement in grid mode.
In one embodiment, a user can manipulate cards in different ways depending on which mode is currently active. In one embodiment, different interactions are available in different modes, and/or certain user actions can be interpreted differently depending on which mode is currently active. The particularities of such differences are described below for various embodiments of the invention.
In one embodiment, cards are active, regardless of the current display mode, so that the information represented in a card is substantially current and is updated substantially in real-time. In one embodiment, the user can interact with cards regardless of display mode, so that user interface elements within cards are active regardless of the display mode. In another embodiment, in some display modes, some or all cards may not be active, so that the data shown therein can be “frozen” while in a particular mode; such an embodiment may be useful, for example, when available system resources preclude real-time updating of all cards without undesirably degrading system performance. Similarly, “frozen” cards may be temporarily inhibited from accepting user input in some embodiments.
In one embodiment, a persistent positional relationship is established and maintained among cards. The positional relationship can be a one-dimensional sequence or some more complex two-dimensional relationship. The positional relationship is persistent in the sense that it does not change unless the user indicates that it should be changed, or some other event takes place that indicates a change is warranted (such as non-use of an application, or an application crashing or being dismissed).
In one embodiment, cards are initially positioned according to the order in which the corresponding activities (such as applications) were launched. New cards can be launched, for example, when a new application or activity is launched, or in some cases for an application that is already running (for example if a new message is being composed in an email application). Thus, in an embodiment where a one-dimensional sequence of cards is implemented, a newly-activated card would be placed at the end of the sequence; for example, if a horizontal row is used, the newly-activated card could be placed to the right of the right-most card in the sequence. A user can, of course, reposition cards as desired.
In one embodiment, if a user launches a new activity (such as an application), a card (or more than one card) for the activity is created, with a position at the end of the sequence. If the user attempts to launch an activity that is already running, in one embodiment the card is not moved within the sequence of cards, but the current view of the sequence is shifted so that the card for the activity is given focus and presented in a central location on the screen. Alternatively, in another embodiment, if the user attempts to launch an activity that is already running, the card for that activity is moved to the end of the sequence.
As described above, in one embodiment, newly opened cards are initially positioned at the end of the sequence. In another embodiment, some newly opened cards may be placed at locations other than at the end of the sequence. For example, any new cards for an already-running activity are placed adjacent to previously existing card(s) for that application. These cards, referred to as “sibling cards”, are therefore positioned so that cards for a given activity are located adjacent to one another in the overall card sequence. For example, a new card for an email application may appear when a user initiates a reply to an email message; the new sibling card for the reply can be positioned adjacent to the existing card for the original message.
In one embodiment, the user is free to move sibling cards so that they are no longer adjacent to one another; in another embodiment, sibling cards cannot be separated from one another, although they can be moved as a group.
In one embodiment, a visual paradigm can be employed to indicate groups of cards. For example, in one embodiment, card groups can be denoted by stacks; all cards within a particular group are displayed in a manner that resembles a stack of cards. Alternatively, card groups can be indicated in other ways that distinguish them from non-grouped cards: for example, card groups can be shown via a distinctive color scheme, different sizes, different vertical or horizontal positioning, bracketing, highlighting, spacing, or any other mechanism. In various embodiments as described below, a user can interact with groups, separating their constituent cards as desired, creating new groups, changing the order of groups, and the like. In one embodiment, where stacking is used to indicate groups, cards can be “unstacked” at times, even while preserving their group relationship, either automatically or manually to facilitate certain types of interactions and viewing of constituent cards. While cards are unstacked, in some embodiments, an alternative mechanism, such as bracketing or distinctive coloring, is used to remind the user that the cards are still members of a group.
The various features described above and herein can be implemented singly or in any combination, as will be apparent to one skilled in the art. Additional features and advantages will become apparent in the description provided below.
The accompanying drawings illustrate several embodiments of the invention and, together with the description, serve to explain the principles of the invention. One skilled in the art will recognize that the particular embodiments illustrated in the drawings are merely exemplary, and are not intended to limit the scope of the present invention.
In the following description, reference is made herein to “activities”. In the context of the present invention, an “activity” is intended to include a software application, a task, a document, a page, and/or any other activity that can be performed in connection with an electronic device. As described herein, the present invention provides techniques for displaying and manipulating representations of activities on an electronic device, using a card metaphor. Thus, activities are represented by “cards”, which is a term used herein to refer to areas of the screen that can be moved and manipulated by the user. Users interact with cards to launch, terminate, and reorder activities, as well as to navigate among activities and perform other operations, as described in more detail below.
System Architecture
In various embodiments, the present invention can be implemented on any electronic device, such as a handheld computer, personal digital assistant (PDA), personal computer, kiosk, cellular telephone, and the like. For example, the invention can be implemented as a feature of an application management paradigm for a software application or operating system running on such a device. Accordingly, the present invention can be implemented as part of a graphical user interface for controlling software on such a device.
In various embodiments, the invention is particularly well-suited to devices such as smartphones, handheld computers, and PDAs, which have limited screen space and which are capable of running several software applications concurrently. One skilled in the art will recognize, however, that the invention can be practiced in many other contexts, including any environment in which it is useful to switch easily and smoothly from one activity to another. Accordingly, the following description is intended to illustrate the invention by way of example, rather than to limit the scope of the claimed invention.
Referring now to
In one embodiment, screen 101 is touch-sensitive, so that a user can activate an application or function by touching a displayed icon 104, 106. In one embodiment, device 100 also includes a touch-sensitive gesture area 102 for entering gesture-based commands, as described in the above-referenced related application. In another embodiment, screen 101 and/or gesture area 102 is sensitive to user motion in proximity to the surface, so as to detect gestures and commands performed near the surface but without necessarily contacting the surface.
For illustrative purposes, device 100 as shown in
In various embodiments, touch-sensitive screen 101 and gesture area 102 can be implemented using any technology that is capable of detecting a location of contact and/or user motion proximate to the surface. Alternatively, the present invention can be implemented with other user input mechanisms, such as a keyboard, trackball, stylus, or the like. One skilled in the art will recognize that the techniques of the present invention are well suited to direct manipulation, but that any input technique can be used. In one embodiment, gesture area 102 provides a touch-sensitive control area extending beyond the edges of touch-sensitive screen 101, as described in related application Ser. No. 12/115,992, filed May 6, 2008, for “Extended Touch-Sensitive Control Area for Electronic Device”, the disclosure of which is incorporated herein by reference.
In one embodiment, device 100 as shown in
Card Metaphor
As described herein, in one embodiment two or more modes are available for interacting with device 100. A determination is made as to which display mode is currently active on device 100. Depending on the current display mode, cards 301 are displayed differently. In various embodiments, display modes can include any combination of the following:
As described in more detail below, device 100 can receive input from the user. In various embodiments, such input can cause device 100 to switch from one display mode to another, and/or to reposition displayed cards in response to user input specifying a switch to another card.
One skilled in the art will recognize that the names given to the modes (“full-screen”, “card”, “shuffle”, and “grid”) are used herein solely for identification purposes, and are not intended to connote any particular characteristic of the modes or restrict the scope of the invention in any other way. In general, and without limiting the scope of the claimed invention: full-screen mode is optimized for maximum use of screen space for interacting with a single activity; card mode is optimized for easily switching focus from one activity to another and for easily initiating and terminating activities; shuffle mode is optimized for reordering and manipulating cards representing activities; and grid mode is optimized to provide an overview of open activities. Many actions can be taken in more than one mode. In one embodiment, activities are live and able to accept input and display output regardless of the current mode; in another embodiment, activities may be live in some modes but not in others. The various modes will be described in more detail below.
Full-Screen Mode
Referring now to
The user interacts with the active activity (such as the calendar application shown in
Card Mode
Referring now to
As can be seen in
In one embodiment, partially displayed cards 301A, 301C provide a positional context for card 301B, and provide a mechanism for navigating to other activities. In one embodiment, the user can designate a card 301A, 301C to have focus by touching any area within the card; this causes the designated card 301 to move to the central portion of display screen 101, and causes other cards to move as well, so that the same positional sequence is maintained. In one embodiment, the user can designate a card 301A, 301C to have focus by dragging any displayed card 301 to cause the desired card 301 to move to the central portion of display screen 101; again, other cards 301 move as well, so that the same positional sequence is maintained. In one embodiment, the user can move cards 301 left and right by dragging a finger along gesture area 102. In one embodiment, such a gesture can be performed even in full-screen mode, causing cards 301 to move left and right in the same manner as described above for card mode.
In response to a user command, cards 301 shift position on screen 101, so that, for example card 301B that currently has focus becomes only partially visible and one of the other cards 301A, 301C becomes fully visible and has focus. The cards 301 move in concert with each other, in response to user commands. Thus, for example, if the user indicates that a central card 301 should move in a rightward direction, then the entire display shifts to the right, as follows:
In one embodiment, the user indicates such movement, for example, by direct manipulation of the displayed cards 301. This can be performed on a touch screen, for example, by dragging the central card 301 to the left or to the right on the screen or by tapping on a card that is partially displayed. Alternatively, a trackball, touch-sensitive pad, or other input device can be provided for facilitating such direct manipulation.
Accordingly, in one embodiment, when the user drags a card 301 to the left or right within display screen 100, other cards 301 move in concert with the dragged card 301. Thus, for example, if the user drags card 301B to the right, cards 301A and 301C move to the right as well. This would cause card 301C to move off the screen, and card 301A would move to the central position of display screen 100. The same result would occur if the user drags card 301A to the right.
In one embodiment, if the user drags cards 301 so as to place a card 301 sufficiently close to the central position to make it clear that the intention is to give the card 301 focus, the card 301 snaps into the central position upon completion of the drag operation. Other cards 301 snap into place accordingly to maintain the same positional sequence. Thus, the user need not drag the card 301 all the way to the central position. If, on the other hand, the user drags cards 301 a small amount that does not cause a new card 301 to be sufficiently close to the central position, all cards 301 snap back to their previous positions upon completion of the drag operation.
In one embodiment, cards 301 show applications or other activities in operation. Thus, as the user navigates among cards 301, he or she can see the actual live application or other activity within each card 301.
In various embodiments, card motion can be constrained to a single axis, for example horizontal or vertical but not both, so as to simplify the positional relationship among cards 301. Alternatively, two or more axes of movements can be made available. In the examples described herein, cards 301 are arranged in a horizontal row. The user moves cards 301 along a horizontal axis to navigate from one activity to another. One skilled in the art will recognize that other arrangements are possible. For example, cards 301 could be arranged vertically instead of horizontally. Alternatively, a two-dimensional arrangement of cards 301 can be provided.
In one embodiment, once the user has moved the desired card 301 to the central position so that it has focus, he or she can indicate that display screen 101 should return to full-screen mode, so that the card 301 having focus occupies substantially the entire display screen 101. Alternatively, device 100 can return to full-screen mode automatically after a period of time elapses where no card movement takes place, or if the user starts to interact with the activity that has focus. In one embodiment, the card 301 that currently has focus is always fully visible and displayed in a substantially central location on display screen 101 with respect to partially displayed cards 301.
Referring now to
In one embodiment, the user can touch or double-tap card 301C to re-enter full-screen mode with the new activity having focus and being active, as shown in
Referring now to
The movement of display screen 101 is conceptual. In actual operation in one embodiment, the switch from card 301B to card 301E is accomplished by moving cards 301 in a leftward direction on screen 101. For example, the user can repeatedly drag cards 301 in a leftward direction to cause cards 301C, 301D, and 301E to successively occupy the central position. Alternatively, the user can click on partially displayed card 301C to move it to the central position and to cause card 301D to be partially displayed, then on partially displayed card 301D to move it to the central position and to cause card 301E to be partially displayed, and then on partially displayed card 301E to move it to the central position. Either mechanism operates to shift focus from the activity represented by card 301B to the activity represented by card 301E.
In one embodiment, a transition effect is performed to enhance the smoothness of the transition as cards 301 move and/or snap into place. In one embodiment, the card 301 that is centrally displayed at any given time is shown slightly larger than other cards 301.
In general, the sequence of cards 301 is persistent, even when the user moves from one card to another 301. In one embodiment, the sequence is circular, so that the rightmost card 301 is considered to be to the left of the left-most card 301. Thus, moving off one end of the sequence takes the user back to the other end of the sequence. In another embodiment, as depicted in
In one embodiment, cards 301 may be moved within the sequence automatically in some circumstances. For example, frequently used cards 301 can be moved to more prominent locations in the sequence, while less frequently used cards 301 can remain in less prominent locations.
Referring now to
Once the telephone application is in the central position in card 301A as shown in
In one embodiment, the user can launch additional activities by returning to the launch screen as shown in
In one embodiment, the user can dismiss activities, for example by closing a card 301. In one embodiment, a card 301 can be closed by clicking on a control within the card. In another embodiment, a card 301 can be closed by dragging the card upward off screen 101, or performing a flicking action in an upward direction. Referring now to
As can be seen in
In one embodiment, dismissing a card 301 causes the application associated with the card to close. In another embodiment, the application remains open even when card 301 is closed.
In one embodiment, a card 301 might close automatically in certain circumstances. For example, if a task associated with an application is completed, or if an application crashes or terminates, the card 301 for the application can close automatically.
In one embodiment, the user can also rearrange cards 301 while in card mode, by tapping and holding a card 301 for a period of time (such as, for example, 500 milliseconds), and then dragging a card 301 from one position to another. An example is shown in
In one embodiment, some visual feedback is provided to indicate that card rearrangement is in progress; for example, the displayed cards 301 can be highlighted in some unique manner, or can include an animation or other effect, once the user has held his or her finger in the appropriate location for at least the specified period of time.
Once the movement action has been initiated, the user can continue to drag card 301 in any direction in order to place card 301 at the desired position within the sequence of cards 301. The sequence of cards 301 scrolls left or right in response to the dragging operation; for example, if the user drags card 301 near the right edge of the screen, the sequence scrolls to the left to cause additional cards 301 in the sequence to be shown while others scroll off the screen. When the user releases card 301, ending the drag operation, card 301 is placed at the indicated position, thus completing the card sequence rearrangement action.
Shuffle Mode
In one embodiment, an additional mode, referred to as “shuffle” mode, provides the user with another mechanism for viewing and rearranging cards. In one embodiment, in shuffle mode, cards 301 are shown at a reduced size, thus permitting more cards 301 to be shown on screen 101 simultaneously.
In one embodiment, when device 100 is in shuffle mode, cards 301 are arranged linearly as they are in card mode. The user can rearrange cards 301 as described above for card mode, and substantially all of the behaviors described above with respect to card mode also apply to shuffle mode. Thus, when the user drags a card 301 to the left or right within display screen 100, other cards 301 move in concert with the dragged card 301. Shuffle mode provides a way to rearrange cards while being able to view more cards 301 simultaneously.
A comparison of
Referring now to
In one embodiment, any number of cards 301 can be completely visible within screen 101. For example, as shown, three cards 301 might be completely visible, with additional partially-visible cards 301 on either side. Alternatively, five cards 301 might be completely visible, with additional partially-visible cards 301 on either side.
In one embodiment, the user can interact with cards 301 in shuffle mode in substantially the same manner as in card mode. Cards 301 can be moved back and forth, and a positional relationship among cards 301 is maintained. Cards 301 can be rearranged within the sequence by dragging and dropping. A card 301 can be closed, and its activity dismissed, by dragging the card 301 upward off screen 101, or performing a flicking action in an upward direction, in a manner similar to the operation described above in connection with
In one embodiment, while in shuffle mode, the user can initiate rearrangement of the card sequence without necessarily first performing a tap-and-hold input operation for some period of time. For example, as shown in
While card rearrangement is taking place, cards 301 shift position to fill gaps, in a manner similar to that described above in connection with
In one embodiment, in shuffle mode, cards 301 show applications or other activities in operation. Thus, as the user navigates among cards 301, he or she can see the actual live application or other activity within each card 301.
Grid Mode
As mentioned above, in one embodiment, both card mode and shuffle mode present cards 301 in a linear arrangement. In one embodiment, a grid mode is available that allows a user to see more cards 301 on screen 101 by presenting cards 301 in a two-dimensional grid.
Referring now to
In one embodiment, when in grid mode, cards 301 are presented at a size that permits all cards 301 to be displayed simultaneously. Thus, for example, in
In one embodiment, in grid mode, a minimum card 301 size (or a maximum number of displayed cards 301) is enforced, even if this means that only a subset of cards 301 can be displayed. Thus, in effect, once cards 301 have been scaled down to the minimum size (or once the maximum number of displayed cards 301 is shown on screen 101), no further downward scaling takes place. Rather, scrolling is permitted to allow the user to access remaining non-displayed cards 301. Some visual indication can be provided to inform the user that additional cards 301 can be accessed via scrolling, for example by showing the edges of cards 301 that are off-screen. The user can scroll, for example, by moving cards 301 to the left or right, or performing a gesture in gesture area 102, or by any other known means. In the example of
Referring now to
If the number of open cards 301 does not exceed the maximum number, then device 100 determines 1404 an appropriate scaling factor to maximize screen size. As described above, in one embodiment, cards are shown at a size that permits all cards 301 to be displayed simultaneously (as long as cards 301 are at least the minimum acceptable size). Device 100 scales 1409 cards 301 according to the scaling factor, and displays 1405 all open cards 301.
If the number of open cards 301 exceeds the maximum number, then device 100 scales 1410 cards 301 to the minimum acceptable size, and displays 1406 a subset of open cards 301 at the minimum acceptable size. Non-displayed cards 301 can be accessed via scrolling. A scroll bar or other scroll mechanism can be shown; alternatively, a user can scroll by dragging cards 301 in a particular direction. If a scroll command is received 1407, device 100 scrolls 1408 the cards so that a different subset of cards 301 is displayed. Scrolling can take place repeatedly, if desired.
In one embodiment, in grid mode, shuffle mode, and card mode, cards 301 show live, real-time information and can be interacted with in the same manner as in full-screen mode. In other embodiments, in at least some of these modes, cards 301 are presented in a “frozen” or static form.
Switching Among Modes
In one embodiment, the user can switch among modes pressing physical button 103 or some other button on device 100. In another embodiment, the user can touch or double-tap a card 301 in shuffle mode to initiate a switch to full-screen mode or to card mode. In yet another embodiment, device 100 switches from shuffle mode to full-screen mode (or to card mode) after some period of inactivity. Other mechanisms can also be provided for switching among the modes. In one embodiment, a transition effect is performed when switching from one mode to another.
In another embodiment, the user can switch among card mode, shuffle mode, and grid mode by tapping in a designated area on screen 101. In one embodiment, the designated area is any area not occupied by any card 301. In another embodiment, the designated area is an area below cards 301.
In yet another embodiment, when in card mode, tapping the area below the row of cards causes a switch to shuffle mode, whereas, when in shuffle mode, tapping any area not occupied by a card 301 causes a switch to card mode. In other embodiments, other user input actions can cause a switch between the modes, including for example, entering a gesture, typing a key on a keyboard, pressing a button, selecting a menu command, activating an on-screen button or other element, or the like.
In another embodiment, the user can switch among the various modes by performing a gesture. One example of such a gesture is a “swipe up” gesture beginning in gesture area 102 and extending onto screen 101. In one embodiment, such a gesture switches from full-screen mode to card mode, or from card mode to shuffle mode, or from shuffle mode to grid mode. In another embodiment, such a gesture switches from full-screen mode to card mode, or from card mode to grid mode. In yet another embodiment, such a gesture switches from full-screen mode to card mode, or from card mode to a launcher screen.
Another example of a mode change gesture is a “swipe down” gesture beginning on screen 101 and extending onto gesture area 102. In one embodiment, such a gesture switches from grid mode to shuffle mode, or from shuffle mode to card mode, or from card mode to full-screen mode. In another embodiment, such a gesture switches from grid mode to card mode, or from card mode to full-screen mode. In yet another embodiment, such a gesture switches from a launcher screen to card mode, or from card mode to full-screen mode.
In other embodiments, other gestures can be used for mode changes; for example, a multi-finger gesture such as a pinch can be used to change from one mode to another.
In another embodiment, the user can switch among modes by initiating a mode change command, for example by touching a button on screen 101, or by pressing button 103 or some other physical button on device 100, or by selecting a mode change command from a menu.
In yet another embodiment, the user can switch from one mode to another by changing the orientation of device 100; for example, device 100 may be equipped with an orientation sensor (such as an accelerometer) that can detect such changes and change modes accordingly.
One skilled in the art will recognize that mode changes can take place in response to other types of commands, contexts, and/or environmental factors.
Auto-Rearrangement of Cards
In some embodiments, device 100 may automatically rearrange cards 301 in response to certain user actions. For example, if the user attempts to launch an activity that already has an open card 301, that card 301 may, in some embodiments, be moved to whatever position would be used for a newly launched activity. In one embodiment, the new position for the card 301 would be the rightmost position in the sequence of cards 301. This may be desirable in order to maintain consistency with regard to the user's expectation that a newly launched activity is positioned at the rightmost position in the sequence.
Referring now to
In
In addition, in one embodiment and as shown in
Alternatively, it may be desirable to shift focus so that, when the user attempts to launch an activity that corresponds to a card 301B that is already open, card 301B is given focus without rearranging the card sequence.
In one embodiment, the user can select whether the card sequence should be rearranged when an activity that corresponds to an open card 301 is launched. This selection can be made in advance, such as via a preferences or options screen. Alternatively, the user can be given an option between the two behaviors at the time the activity corresponding to an open card 301 is launched. For example, the user can be presented with a dialog box noting that the activity is already open, and prompting the user to indicate whether or not to rearrange the card sequence.
Although
Referring now to
If, in step 1502, a card 301 for the launched activity is already open, device 100 determines 1505 whether it should automatically rearrange the card sequence. As discussed above, in some embodiments card sequences are automatically rearranged when an activity that corresponds to an open card 301 is launched, while in other embodiments, they are not. Alternatively, the user can be given an option to select between the two behaviors, either in advance or at the time the activity corresponding to an open card 301 is launched.
If device 100 determines 1505 that it should automatically rearrange the card sequence, the card 301 corresponding to the launched activity is moved 1507 to the end of the current sequence of cards 301 (for example, by moving the card 301 corresponding to the launched activity to the rightmost position in the sequence of cards 301).
In one embodiment, whether or not the card sequence is rearranged, focus is shifted 1506 to the card 301 corresponding to the launched activity, for example by placing the card 301 in the center of screen 101, or causing the activity represented by the card 301 to occupy substantially entire screen 101 (if in full-screen mode).
Sibling Cards
In one embodiment, when a new card 301 is opened, its placement within the sequence of cards 301 depends upon its relationship (if any) with existing open cards 301. For example, if a new card 301 is opened for an already-running activity, the new card 301 can be placed adjacent to open card(s) 301 for that application. These cards 301, referred to as “sibling cards”, are therefore positioned so that cards 301 for a given activity are located adjacent to one another in the overall card sequence. For example, a new card 301 for an email application may appear when a user initiates a reply to an email message; the new sibling card 301 for the reply can be positioned adjacent to the existing card 301 for the original message. As another example, a new card 301 for a browser application can be positioned adjacent to any currently open cards 301 for the browser application. Placing related cards 301 so that they are adjacent to each other allows a user to more easily discern the relationship among cards 301 in the sequence and to navigate among cards 301.
Cards 301 can be related to one another (i.e., can be “siblings”) by virtue of the fact that they are associated with a common application or activity. Alternatively, cards can be considered siblings if they relate to a particular task, thread, contact, subject, company, or operation. The sibling relationship can be inferred, or it can be established based on explicit labeling or other indication specified by a user. One skilled in the art will recognize that the mechanism for placing cards 301 according to their sibling relationship can be used regardless of the particular basis for determining a sibling relationship among cards 301.
In one embodiment, sibling cards 301 can be freely moved and/or separated as the user wishes. Thus, the initial placement of a new card 301 by virtue of its sibling relationship with open card(s) 301 does not prohibit later movement of the card 301 to a location that is not adjacent to its siblings 301.
Referring now to
In
Although
Referring now to
In another embodiment, sibling cards do move together, so that dragging card 301D would cause card 301D′ to move as well. For example, in one embodiment, sibling cards 301 cannot be separated from one another.
In another embodiment, the user can specify whether or not sibling cards 301 should move together, either in advance via a preference screen or similar mechanism, or at the time the user initiates a card movement operation involving a card 301 having a sibling.
In another embodiment, the user can select more than one card 301 to be moved simultaneously. For example, the user can highlight two or more cards 301, and then move one of the highlighted cards 301 to cause all of them to move together. In one embodiment, selecting a card 301 that has at least one sibling causes the sibling(s) to be selected automatically, so that if the user then moves one of the selected cards 301 the siblings move as well; however, the user can deselect the selected cards 301 prior to moving the cards 301, if he or she does not want all of the sibling cards to move 301.
Card Groups
In one embodiment, cards 301 can be visually grouped with one another. Thus, cards 301 having some relationship to one another (such as cards 301 associated with a particular application or activity) can be displayed in a manner that indicates and/or reinforces the relationship. For example, cards 301 representing various web pages being viewed via a browser application can be grouped.
One example of a visual paradigm for indicating groups of cards 301 is to depict the cards 301 in a manner that resembles a stack or deck, with a fully-visible front card 301 (or “top card”) and one or more additional cards 301 depicted as though they are behind the front card 301. Alternatively, card groups can be indicated in other ways that distinguish them from non-grouped cards 301: for example, card groups can be shown via a distinctive color scheme, different sizes, different vertical or horizontal positioning, bracketing, highlighting, spacing, or any other mechanism. In various embodiments as described below, a user can interact with groups, separating their constituent cards 301 as desired, creating new groups, changing the order of groups, and the like. In one embodiment, where stacking is used to indicate groups, cards 301 can be “unstacked” at times, even while preserving their group relationship, either automatically or manually to facilitate certain types of interactions and viewing of constituent cards 301. While cards 301 are unstacked, in some embodiments, an alternative mechanism, such as bracketing or distinctive coloring, is used to remind the user that the cards 301 are still members of a group. For example, in one embodiment, card groups are represented by stacks in card view, but the stacks are separated in full-screen view so that the user can see each constituent card 301 in its entirety.
Referring now to
In one embodiment, the user can move and manipulate stack 1301A as if it were a single card 301, including rearranging stack 1301A within the card sequence, dismissing stack 1301A, and the like. In one embodiment, the user can dismiss the entire group of cards by performing a card dismissal operation on stack 1301A (such as dragging stack 1301A up to the top of screen 101). In another embodiment, such a dismissal action only dismisses the top card in the group while leaving the remaining card(s) 301 still open (and still grouped if there are more than one). In yet another embodiment, in response to a user action to dismiss stack 1301A, the user is prompted to specify whether he or she intends to dismiss the entire group or a single card 301.
In one embodiment, the user can cause cards 301 in a stack 1301A to be reordered, so as to bring a different card 301 to the top of the stack 1301A for ease of viewing. In one embodiment, the user drags the front card (such as card 301C in
If the user causes a switch from card mode to full-screen mode, in one embodiment cards 301 in a stack 1301A are “unstacked” so that the full-screen mode resembles that shown in
As mentioned above, in various embodiments card groups can be shown in other ways. For example, in one embodiment, card size and/or vertical offset can be used to indicate cards 301 that are part of a group. For example, in
In one embodiment, some of the cards 301 in the group are shown in front of, and partially obscuring, other cards 301 that are not part of the group. For example, in
In one embodiment, if focus changes so that the card 301 in focus is not a member of group 1301B, the depiction of group 1301B changes to a stack view. Thus, in this embodiment, the mechanism for depicting groups in
In one embodiment, card size and/or vertical offset can be used to depict card groups in both card mode and shuffle mode. In another embodiment, card groups are depicted in card mode by vertical offset and distinctive card size (as shown in
In one embodiment, cards 301 are automatically grouped with one another, for example when several cards 301 are associated with a common application or other activity. In one embodiment, the user can manually add cards 301 to groups, or remove cards 301 from groups. In shuffle mode and/or in card mode, a user can add a card 301 to a group by dragging the card 301 to an area of the screen occupied by a card group. Referring now to
In shuffle mode and/or in card mode, a user can remove a card 301 from a group by dragging the card 301 to an area of the screen not occupied by a card group. Referring now to
In one embodiment, a user can manually create a new group and add cards 301 to it. For example, referring now to
One skilled in the art will recognize that the technique depicted in
In one embodiment, visual feedback is provided while a user is dragging a card 301 onto a group or otherwise performing an input operation that can add a card 301 to a group. For example, a distinctive highlighting effect, such as a glow, can be applied to a group while the user drags a card 301 onto the group but before he or she completes the drag-and-drop operation. This highlighting effect can serve to inform the user that, if he or she drops the card 301 it will be placed in the group.
In one embodiment, the vertical offset at which a user drops a card 301 is relevant only when it is needed to disambiguate a card rearrangement action from an action intended to add/remove a card 301 to/from a group. For example, if a user drags and drops a card 301 between two cards 301 that are already part of a group, then the vertical offset of the card being dragged is not relevant; once dropped, the card 301 joins the group. On the other hand, if a user drags and drops a card 301 between a card 301 that is part of a group and an adjacent card that is not part of the group, the vertical offset of the card at the time it is dropped is relevant to determining whether to a) add the card 301 to the group or b) move the card 301 to a location adjacent to (but not part of) the group.
For example, referring again to
In one embodiment, a user can turn card grouping on or off, for example via a preferences or options screen. If card grouping is turned off, all cards 301 are represented singly and without reference to groups. In one embodiment, grouping relationships are preserved internally when card grouping is turned off, so that the groups can be reestablished if card grouping is later turned on.
In one embodiment, groups can be nested, so that a group can contain another group as one of its members. Any number of levels of such nesting can be implemented. In one embodiment, successively nested groups can be indicated, for example, by different offsets in vertical position on screen 101.
In various embodiments, the present invention can be implemented as a system or a method for performing the above-described techniques, either singly or in any combination. In another embodiment, the present invention can be implemented as a computer program product comprising a computer-readable storage medium and computer program code, encoded on the medium, for performing the above-described techniques.
The various features described above can be implemented singly or in any combination, as will be apparent to one skilled in the art.
The present invention has been described in particular detail with respect to one possible embodiment. Those of skill in the art will appreciate that the invention may be practiced in other embodiments. First, the particular naming of the components, capitalization of terms, the attributes, data structures, or any other programming or structural aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, formats, or protocols. Further, the system may be implemented via a combination of hardware and software, as described, or entirely in hardware elements, or entirely in software elements. Also, the particular division of functionality between the various system components described herein is merely exemplary, and not mandatory; functions performed by a single system component may instead be performed by multiple components, and functions performed by multiple components may instead be performed by a single component.
Reference herein to “one embodiment”, “an embodiment”, or to “one or more embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least one embodiment of the invention. Further, it is noted that instances of the phrase “in one embodiment” herein are not necessarily all referring to the same embodiment.
Some portions of the above are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps (instructions) leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise manipulated. It is convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. Furthermore, it is also convenient at times, to refer to certain arrangements of steps requiring physical manipulations of physical quantities as modules or code devices, without loss of generality.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “displaying” or “determining” or the like, refer to the action and processes of a computer system, or similar electronic computing module and/or device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system memories or registers or other such information storage, transmission or display devices.
Certain aspects of the present invention include process steps and instructions described herein in the form of an algorithm. It should be noted that the process steps and instructions of the present invention can be embodied in software, firmware or hardware, and when embodied in software, can be downloaded to reside on and be operated from different platforms used by a variety of operating systems.
The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Further, the computers referred to herein may include a single processor or may be architectures employing multiple processor designs for increased computing capability.
The algorithms and displays presented herein are not inherently related to any particular computer, virtualized system, or other apparatus. Various general-purpose systems may also be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will be apparent from the description above. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references above to specific languages are provided for disclosure of enablement and best mode of the present invention.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the above description, will appreciate that other embodiments may be devised which do not depart from the scope of the present invention as described herein. In addition, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the claims.
The present application is a continuation of U.S. patent application Ser. No. 12/416,279, filed Apr. 1, 2009, for “Card Metaphor For Activities In A Computing Device”, which claims priority as a continuation-in-part of U.S. patent application Ser. No. 12/126,145, filed May 23, 2008, for “Navigating Among Activities in a Computing Device”, now U.S. Pat. No. 8,296,684, the disclosures of all of which are incorporated herein by reference. The present application is related to U.S. patent application Ser. No. 12/115,992, filed May 6, 2008, for “Extended Touch-Sensitive Control Area for Electronic Device”, the disclosure of which is incorporated herein by reference. The present application is related to U.S. patent application Ser. No. 11/379,552, filed Apr. 20, 2006, for “Keypad and Sensor Combination to Provide Detection Region that Overlays Keys”, the disclosure of which is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4680577 | Straayer et al. | Jul 1987 | A |
| 5146556 | Hullot et al. | Sep 1992 | A |
| 5499330 | Lucas et al. | Mar 1996 | A |
| 5574846 | Yoshimura et al. | Nov 1996 | A |
| 5586244 | Berry et al. | Dec 1996 | A |
| 5675361 | Santilli | Oct 1997 | A |
| 5677708 | Matthews, III et al. | Oct 1997 | A |
| 5766708 | Panizza | Jun 1998 | A |
| 6011537 | Slotznick | Jan 2000 | A |
| 6061050 | Allport et al. | May 2000 | A |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6407757 | Ho | Jun 2002 | B1 |
| 6441811 | Sawada et al. | Aug 2002 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6590593 | Robertson et al. | Jul 2003 | B1 |
| 6600936 | Kaerkkaeinen et al. | Jul 2003 | B1 |
| 6613100 | Miller | Sep 2003 | B2 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6680677 | Tiphane | Jan 2004 | B1 |
| 6686906 | Salminen et al. | Feb 2004 | B2 |
| 6765559 | Hayakawa | Jul 2004 | B2 |
| 6924789 | Bick | Aug 2005 | B2 |
| 6958749 | Matsushita et al. | Oct 2005 | B1 |
| 6992658 | Wu et al. | Jan 2006 | B2 |
| 7030861 | Westerman et al. | Apr 2006 | B1 |
| 7051291 | Sciammarella | May 2006 | B2 |
| 7151528 | Taylor et al. | Dec 2006 | B2 |
| 7159176 | Billmaier et al. | Jan 2007 | B2 |
| 7170500 | Canova et al. | Jan 2007 | B2 |
| 7352363 | Coates et al. | Apr 2008 | B2 |
| 7360166 | Krzanowski | Apr 2008 | B1 |
| 7394452 | Wong et al. | Jul 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7610599 | Nashida | Oct 2009 | B1 |
| 7650569 | Allen et al. | Jan 2010 | B1 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7705830 | Westerman et al. | Apr 2010 | B2 |
| D615989 | Chaudhri | May 2010 | S |
| 7770136 | Beeck et al. | Aug 2010 | B2 |
| 7800592 | Kerr et al. | Sep 2010 | B2 |
| 7934168 | Sakamoto et al. | Apr 2011 | B2 |
| 8001479 | Katsuranis et al. | Aug 2011 | B2 |
| 8001488 | Lam | Aug 2011 | B1 |
| 8019388 | Chiam | Sep 2011 | B2 |
| 8159469 | Shiplacoff et al. | Apr 2012 | B2 |
| 8296684 | Duarte et al. | Oct 2012 | B2 |
| 8373673 | Shiplacoff et al. | Feb 2013 | B2 |
| 8448083 | Migos et al. | May 2013 | B1 |
| 8683362 | Shiplacoff et al. | Mar 2014 | B2 |
| 20020032554 | Nakagawa | Mar 2002 | A1 |
| 20020089536 | Dang | Jul 2002 | A1 |
| 20020109735 | Chang et al. | Aug 2002 | A1 |
| 20020191013 | Abrams | Dec 2002 | A1 |
| 20030071849 | Ferri | Apr 2003 | A1 |
| 20030085870 | Hinckley | May 2003 | A1 |
| 20030148799 | Chen | Aug 2003 | A1 |
| 20030222917 | Trantow | Dec 2003 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040181804 | Billmaier | Sep 2004 | A1 |
| 20040189720 | Wilson et al. | Sep 2004 | A1 |
| 20040193413 | Wilson et al. | Sep 2004 | A1 |
| 20050003851 | Chrysochoos et al. | Jan 2005 | A1 |
| 20050021336 | Katsuranis | Jan 2005 | A1 |
| 20050024322 | Kupka | Feb 2005 | A1 |
| 20050057524 | Hill et al. | Mar 2005 | A1 |
| 20050071761 | Kontio | Mar 2005 | A1 |
| 20050078093 | Peterson et al. | Apr 2005 | A1 |
| 20050088416 | Hollingsworth | Apr 2005 | A1 |
| 20050102638 | Jiang et al. | May 2005 | A1 |
| 20050131945 | Muller et al. | Jun 2005 | A1 |
| 20050149879 | Jobs et al. | Jul 2005 | A1 |
| 20050188329 | Cutler et al. | Aug 2005 | A1 |
| 20050190280 | Haas et al. | Sep 2005 | A1 |
| 20050192924 | Drucker et al. | Sep 2005 | A1 |
| 20050243053 | Liess et al. | Nov 2005 | A1 |
| 20060007181 | Jung et al. | Jan 2006 | A1 |
| 20060010395 | Aaltonen | Jan 2006 | A1 |
| 20060015878 | Ritter | Jan 2006 | A1 |
| 20060053387 | Ording | Mar 2006 | A1 |
| 20060075348 | Xu et al. | Apr 2006 | A1 |
| 20060085757 | Andre et al. | Apr 2006 | A1 |
| 20060125962 | Shelton et al. | Jun 2006 | A1 |
| 20060181548 | Hafey et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060218504 | Hiroi et al. | Sep 2006 | A1 |
| 20060224989 | Pettiross et al. | Oct 2006 | A1 |
| 20060267951 | Rainisto | Nov 2006 | A1 |
| 20070101292 | Kupka | May 2007 | A1 |
| 20070101297 | Forstall et al. | May 2007 | A1 |
| 20070152978 | Kocienda et al. | Jul 2007 | A1 |
| 20070152984 | Ording et al. | Jul 2007 | A1 |
| 20070165004 | Seelhammer et al. | Jul 2007 | A1 |
| 20070177803 | Elias et al. | Aug 2007 | A1 |
| 20070220440 | Song et al. | Sep 2007 | A1 |
| 20070226647 | Louch | Sep 2007 | A1 |
| 20070245263 | Hale et al. | Oct 2007 | A1 |
| 20070247431 | Skillman et al. | Oct 2007 | A1 |
| 20070273668 | Park et al. | Nov 2007 | A1 |
| 20070277124 | Shin et al. | Nov 2007 | A1 |
| 20070288860 | Ording et al. | Dec 2007 | A1 |
| 20070296709 | GuangHai | Dec 2007 | A1 |
| 20080001924 | de los Reyes | Jan 2008 | A1 |
| 20080034317 | Fard et al. | Feb 2008 | A1 |
| 20080055265 | Bewley et al. | Mar 2008 | A1 |
| 20080062139 | Hotelling et al. | Mar 2008 | A1 |
| 20080062140 | Hotelling et al. | Mar 2008 | A1 |
| 20080062147 | Hotelling et al. | Mar 2008 | A1 |
| 20080062148 | Hotelling et al. | Mar 2008 | A1 |
| 20080064499 | Grant et al. | Mar 2008 | A1 |
| 20080082930 | Omernick et al. | Apr 2008 | A1 |
| 20080084400 | Rosenberg | Apr 2008 | A1 |
| 20080084440 | Omata et al. | Apr 2008 | A1 |
| 20080089587 | Kim et al. | Apr 2008 | A1 |
| 20080100593 | Skillman et al. | May 2008 | A1 |
| 20080104544 | Collins et al. | May 2008 | A1 |
| 20080148149 | Singh et al. | Jun 2008 | A1 |
| 20080168401 | Boule et al. | Jul 2008 | A1 |
| 20080168403 | Westerman et al. | Jul 2008 | A1 |
| 20080168405 | Tolmasky et al. | Jul 2008 | A1 |
| 20080177994 | Mayer | Jul 2008 | A1 |
| 20080204402 | Hirata et al. | Aug 2008 | A1 |
| 20080256472 | Kim et al. | Oct 2008 | A1 |
| 20080281689 | Blinnikka et al. | Nov 2008 | A1 |
| 20080297484 | Park et al. | Dec 2008 | A1 |
| 20080303794 | Bolt et al. | Dec 2008 | A1 |
| 20080307335 | Chaudhri et al. | Dec 2008 | A1 |
| 20080316183 | Westerman et al. | Dec 2008 | A1 |
| 20090013282 | Mercer | Jan 2009 | A1 |
| 20090019031 | Krovitz et al. | Jan 2009 | A1 |
| 20090070691 | Jain | Mar 2009 | A1 |
| 20090085886 | Huang et al. | Apr 2009 | A1 |
| 20090106694 | Kraft | Apr 2009 | A1 |
| 20090164928 | Brown et al. | Jun 2009 | A1 |
| 20090183120 | Ording et al. | Jul 2009 | A1 |
| 20090193364 | Jarrett et al. | Jul 2009 | A1 |
| 20090199241 | Unger et al. | Aug 2009 | A1 |
| 20090217198 | Jung | Aug 2009 | A1 |
| 20090278806 | Duarte et al. | Nov 2009 | A1 |
| 20100081475 | Chiang et al. | Apr 2010 | A1 |
| 20100122290 | Allen et al. | May 2010 | A1 |
| 20100156656 | Duarte et al. | Jun 2010 | A1 |
| 20100156813 | Duarte et al. | Jun 2010 | A1 |
| 20100169766 | Duarte et al. | Jul 2010 | A1 |
| 20100211872 | Rolston et al. | Aug 2010 | A1 |
| 20100214278 | Miura | Aug 2010 | A1 |
| 20100295801 | Bestle et al. | Nov 2010 | A1 |
| 20110093494 | Chandler | Apr 2011 | A1 |
| 20120084711 | Duarte et al. | Apr 2012 | A1 |
| 20120278756 | Shah | Nov 2012 | A1 |
| 20130298057 | Duarte et al. | Nov 2013 | A1 |
| 20140258897 | Shiplacoff et al. | Sep 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2008100003 | Feb 2008 | AU |
| 1896921 | Jan 2007 | CN |
| 101167045 | Apr 2008 | CN |
| 101390039 | Mar 2009 | CN |
| 0548646 | Jun 1993 | EP |
| 1462921 | Sep 2004 | EP |
| 1688830 | Aug 2006 | EP |
| 1942402 | Jul 2008 | EP |
| 1962480 | Aug 2008 | EP |
| 2068236 | Jun 2009 | EP |
| 2076000 | Jul 2009 | EP |
| 2480777 | Nov 2011 | GB |
| WO-2008030976 | Mar 2008 | WO |
| WO-2009080653 | Jul 2009 | WO |
| WO-2010096219 | Aug 2010 | WO |
| Entry |
|---|
| “threshold” and related definitions: IEEE 100, The Authoritative Dictionary of IEEE Standards Terms, 7th edition, copyright 2000 by The Institute of Electrical and Electronics Engineers. ISBN 0-7381-2601-2., pp. 1177-1178. |
| Threshold. (1992). In C. Morris (Ed.), Academic press Dictionary of science and technology. Oxford, United Kingdom: Elsevier Science & Technology. Retrieved from http://search.credoreference.com/content/entry/apdst/threshold/0. |
| “Designing for the Multitasker,” Internet Article, Publication Date: Mar. 17, 2010; <http://blog.graphicpeel.com/post/454779602/designing-for-the-multitasker>. |
| Extended European Search Report, European Application No. 09751303.0, Date: Apr 2, 2012, pp. 1-6. |
| Extended European Search Report, European Application No. 09751304.8, Date: Apr. 3, 2012, pp. 1-6. |
| International Search Report mailed Oct. 30, 2009, issued in international application No. PCT/US2009/044389. |
| International Search Report mailed Oct. 30, 2009, issued in international application No. PCT/US2009/044390. |
| iPhone User's Guide, Chapter 5, pp. 58-59, Apple Safari Browser, “Opening Multiple Webpages at Once,”(2007). |
| Moyle, Michael et al., The Design and Evaluation of Flick Gesture for ‘Back’ and ‘Forward’ in Web Browsers, Proceedings of the Fourth Australian user interface conference on User interfaces 2003, Volume 18, Australian Computer Society, Inc. Darlinghurst, Australia, copyright 2003, ISBN:0-909925-96-8. 8 pages. |
| Written Opinion—PCT/US2009/044389—ISA/EPO—Oct. 30, 2009. |
| Written Opinion—PCT/US2009/044390—ISA/EPO—Oct. 30, 2009. |
| Number | Date | Country | |
|---|---|---|---|
| 20140157191 A1 | Jun 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12416279 | Apr 2009 | US |
| Child | 14174525 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12126145 | May 2008 | US |
| Child | 12416279 | US |
