Patent Description:
<CIT> describes a dual-screen user device and methods for revealing a combination of desktops on single and multiple screens. Selected desktops and/or running applications are displayed on dual screen displays. Desktops and applications can be shifted between screens by user gestures, and/or moved off of the screens and therefore hidden. Hidden desktops and screens can be re-displayed by yet other gestures. The desktops and applications are arranged in a window stack that represents a logical order of the desktops and applications providing a user with an intuitive ability to manage multiple applications/desktops running simultaneously. One user gesture launches an applications management window that provides visual indications of all of the applications and desktops running at the time, applications/desktops displayed on the screens. Other gestures can rearrange the order of all of the applications and desktops in the window stack.

<CIT> describes a method that includes receiving a user input at a first display surface of an electronic device to move a graphical user interface element displayed at the first display surface. The electronic device includes a second display surface separated from the first display surface by a gap. The method also includes determining that at least a portion of the graphical user interface element is to be moved beyond an edge of the first display surface into the gap such that the at least a portion of the graphical user element will not be displayed at the first display surface. The method further includes displaying the at least a portion of the graphical user interface element at the second display surface based on a location and a direction of movement of the graphical user interface element at the first display surface.

<CIT> describes a portable device comprising a first touch-screen display and a second touch-screen display arranged on at least one foldable panel, and a method for controlling the portable device. In certain examples, a portable device displays pieces of information linked to each other through two touch-screen displays, and a user may interact with the portable device through a touch gesture sensed in at least one of the two touch-screen displays. In certain examples, a portable device portable device provides, through two touch-screen displays, dual homepages, mode-switching capability, a pocket mode homepage screen, a gallery map, a tack manager, a private broadcast, a clipboard, an electronic book, a video conference, a cooperative game, a calendar, a phone conversation, a camera, mode-switching capability by sensing the folding/un-folding of the panel, and/or the display of information over a hinge between panels.

Examples are disclosed that relate to operating a user interface of a multi-screen computing device. One example provides a computing device, comprising a first portion comprising a first display and a first touch sensor, and a second portion comprising a second display and a second touch sensor, the second portion connected to the first portion via a hinge, the hinge defining a seam between the first display and the second display. The computing device is configured to receive a touch input at the first display moving an application that is currently displayed on the first display and not on the second display toward the second display, detect the touch input releasing the application within a predetermined area, span the application across the first display and the second display such that a portion of application content is hidden behind the seam, receive a touch input moving the spanned application, and move the spanned application in a direction of the touch input to reveal at least a portion of the application content hidden behind the seam.

Another example provides a computing device, comprising a first portion comprising a first display and a first touch sensor, a second portion comprising a second display and a second touch sensor, the second portion connected to the first portion via a hinge, the hinge defining a seam between the first display and the second display, a logic device, and a storage device holding instructions executable by the logic machine. The instructions are executable to receive a touch input at the first display moving an application from the first display toward the second display, when the touch input releases the application within a first predefined area, to move the application to the second display, and when the touch input releases the application within a second predetermined area, to span the application by displaying the application across the first display and the second display.

Another example provides a method enacted on a computing device, the computing device comprising a first portion comprising a first display and a first touch sensor, and a second portion comprising a second display and a second touch sensor, the second portion connected to the first portion via a hinge. The method comprises displaying a first application on the first display, displaying a second application on the second display, receiving a touch input at the first display moving the first application toward the second display, detecting the touch input releasing the application within a predetermined area, and stacking the first application over the second application on the second display based at least upon the touch input releasing the application within the predetermined area.

The disclosed examples relate to a computing device having a multi-screen configuration. <FIG> shows an example multi-screen computing device in the form of a dual-screen computing device <NUM>. The computing device <NUM> includes a first portion <NUM> and a second portion <NUM> that respectively include a first display <NUM> and a second display <NUM>. A hinge <NUM> arranged between the first and second portions <NUM> and <NUM> allows the relative pose between the portions and their displays to be adjusted. The computing device <NUM> may be configured to determine the relative pose between the first and second portions <NUM> and <NUM> (e.g. via motion sensor data from one or more motion sensors in each portion), and adjust a function of the computing device based on the relative pose.

Each of the first display <NUM> and the second display <NUM> may be a touch-sensitive display having a touch sensor. The touch sensor(s) may be configured to sense multiple sources of touch input, such as a digit of a user and a stylus manipulated by the user, and may sense multiple concurrent touches. The computing device <NUM> may assume any suitable form, including but not limited to various mobile devices (e.g., foldable smart phone, tablet, or laptop).

The first portion <NUM> includes a first three-dimensional pose sensor system <NUM> configured to provide output indicative of a three-dimensional pose of the first portion <NUM>, and the second portion <NUM> includes a second three-dimensional pose sensor system <NUM> configured to provide output indicative of a three-dimensional pose of the second portion <NUM>. In some examples, the first and second pose systems <NUM> and <NUM> each includes an accelerometer and a gyroscope, and optionally a magnetometer. The output produced by the first and second pose systems <NUM> and <NUM> may be used to determine a three-dimensional pose of first and second portions <NUM> and <NUM>, respectively. In other examples, any other suitable sensor or sensors may be used to sense the relative orientations of the displays, such as an optical or mechanical encoder incorporated into the hinge.

<FIG> show various example display poses for the dual-screen computing device <NUM>. More specifically, <FIG> shows a single portrait pose (in which either display <NUM> or <NUM> may face the user), <FIG> shows a double portrait pose, <FIG> shows a single landscape pose (in which either display <NUM> or <NUM> may face the user), and <FIG> shows a double landscape pose. Depending on a pose of the computing device <NUM>, a user interface of the computing device <NUM> may be configured to operate in a certain manner and/or respond to touch inputs differently. For example, in <FIG>, the second portion <NUM> may be folded via the hinge <NUM> behind the first portion <NUM>, or vice versa. From the perspective of a user of the computing device <NUM>, when the second display is folded behind the first portion, the second display <NUM> may be imperceptible. As such, the computing device <NUM> may render graphical content that was previously displayed across both the first display <NUM> and the second display <NUM> fully onto the first display <NUM>, may cease displaying images on the second display <NUM>, and/or may also cease receiving touch inputs on the second display <NUM>. Various examples of operating a user interface and responding to touch inputs based on the pose of the computing device are further described below.

In some examples, a touch input may span an application across both a first display and a second display of a dual-screen device. <FIG> and <FIG> show an example user interface displayed when spanning an application <NUM> across the first display <NUM> and the second display <NUM> of the first portion <NUM> and the second portion <NUM> of the dual-screen device <NUM>. First, the user interface at <NUM> shows application <NUM> open on the second display <NUM> of the second portion <NUM>, while the first display <NUM> on the first portion <NUM> is unoccupied by any applications. At <NUM>, the user interface shows that a touch input <NUM> has dragged the application <NUM> from the second display <NUM> toward the first display <NUM>. The touch input <NUM> may originate at a location along an application navigation bar <NUM> that is displayed at the bottom of the application <NUM>. The application navigation bar <NUM> may be configured to receive user inputs related to moving, dismissing, or otherwise manipulating the application <NUM>. The touch input <NUM> may release the application <NUM> when the application <NUM> is in a predetermined area, e.g. within a threshold distance from a seam <NUM> in between the two displays (as defined by the hinge <NUM> that connects the two device portions). Example predetermined areas for triggering certain user interface actions are discussed in more detail in regard to <FIG>.

The user interface at <NUM> shows the application <NUM> spanned across both displays in response to the touch input releasing the application <NUM>. A mask may be applied to a rendering of the application in a location corresponding to the seam <NUM> when the application is spanned. Such masking may help the display of the spanned application (and also application windows moving across the seam) to appear more natural, as opposed to splitting the full image between the two displays. However, such masking also causes a small area of the displayed application to be unviewable. As such, a user may desire to reveal the content being blocked by the seam. <FIG> at <NUM> and <NUM> show example interactions in which a user moves the application <NUM> (e.g. by touching and dragging) to reveal content hidden by the seam <NUM>. Any suitable touch inputs may trigger offsetting of the application to reveal content behind the seam <NUM>. As examples, a touch input may swipe, touch and drag, or perform a multi-finger gesture to the left or right from the seam, from a seam corner, etc. in double portrait mode. The same touch inputs may apply except in up or down directions from the seam in double landscape mode. At <NUM>, the user interface shows a touch input moving the application toward the left, and at <NUM>, the user interface shows a touch input moving the application toward the right. The spanned application may thereby be moved in a direction of the touch input to reveal at least a portion of the application content hidden behind the seam. In either example, a user may then move the application back to the original spanned mode shown at <NUM>, such as by tapping a revealed arrow user interface control <NUM> or <NUM> (shown at <NUM> and <NUM>), or by dragging and releasing the application back toward the seam. In other examples, such masking may not be applied, and instead the application may be divided into two portions that together make up the entire image. In yet other examples, such a seam between multiple displays may not be present, or a seam may also be configured to display content (e.g. via a flexible display over the hinge).

In some examples, a touch input may move an application while scaling the application simultaneously. <FIG> illustrate an example of the scaling of a displayed application in response to a user touch input dragging the application. As shown, an origin of the scaling of the application may be set dynamically by horizontal touch position. For example, <FIG> shows a touch input <NUM> that starts at a right bottom corner of the application, <FIG> shows a touch input <NUM> that starts at a middle of the bottom of the application, and <FIG> shows a touch input <NUM> that starts at a left bottom corner of the application. In these examples, the scaling decreases based upon a vertical movement distance from the bottom of the display, and an origin of the movement is based upon the initial touch location of the touch input. The dynamic positioning of the origin of scaling may help to create the effect that the application follows the user's finger or stylus. The automatic scaling that occurs with movement of an application may help to better indicate to the user that the application is currently being moved while keeping the content of the application visible. Further, once released, expansion of the application back to its original size may also help to better indicate to the user that the application is no longer being moved by user input. Automatic scaling when moving an application may further help provide a more seamless transition of the application to a recent applications list or task switcher for switching between applications, as examples. For example, a preview for a recent applications list may be triggered when a gesture velocity for moving application drops to within a threshold velocity close to zero.

In some examples, an application may be moved in response to a horizontal movement and scaled in response to a vertical movement in portrait poses, and moved in response to a vertical movement and scaled in response to a horizontal movement in landscape poses. Further, the ratio of movement of the touch input to movement of the application on the user interface may change as a function of touch position. <FIG> shows a plot of an example vertical movement of an application on a display as a function of touch position in a Y direction when the display device is in a portrait pose. In this example, the position of an application follows a user's touch in a <NUM>:<NUM> ratio from a Y position of pixel <NUM> to pixel <NUM>. Next, from a Y of touch from pixels <NUM> to <NUM>, the change in Y position of the application compared to the change in touch location varies at a ratio of less than <NUM>: <NUM> from pixels <NUM> to <NUM>. From Y of touch at pixels <NUM> to <NUM>, the Y position of the application versus the touch position linearly varies at even a lesser ratio. In other examples, any other suitable mapping of touch movement to application movement may be used.

Likewise, the application scaling also may change as a function of touch position. <FIG> shows a plot of an example application scaling as a function of touch position in a Y direction. From Y of touch at pixels <NUM> to <NUM>, the application may scale linearly at a first rate from <NUM>% to <NUM>% scale; from Y of touch at pixels <NUM> to <NUM>, the application may scale linearly, but at a lesser rate, from <NUM>% to <NUM>% scale; and from Y of touch less than <NUM>, the scale of the application may remain at <NUM>%, thus not decreasing further. In the depicted example, movement of the application in a horizontal direction while in a portrait mode may follow the user's touch in a <NUM>:<NUM> ratio at all positions of X, and horizontal movement may not cause the application to scale, as an example. Movement of an application in a landscape mode also may display movement rate and/or scaling adjustments.

In double portrait and double landscape poses, movement of the applications from one display to the other display may be accompanied by hint images that are displayed to indicate how an application may move or behave based on the touch input. <FIG> show example hint images <NUM> and <NUM> that may be displayed while moving an application in a double portrait pose and a double landscape pose, respectively. The illustrated example hint images indicate that if a touch input currently dragging the application were to be released at the current location, then the application would snap to or move to the display on which hint image is displayed.

<FIG> show example hint images displayed based on touch inputs moving an application to within example threshold distances. In these figures, a transition zone <NUM> occupies a portion of the first display, and a portion of the second display. <FIG> illustrates an example in which a touch input drags an application from the second display toward the first display. In this figure, a first fraction <NUM> of the application, as defined from a left edge of the application to example line A, has not passed a first boundary <NUM> of the transition zone <NUM>, and no hint images are yet displayed, indicating that if the touch input were to release the application at that position, the application would be displayed again at the original position without any movement.

<FIG> shows the application having been moved sufficiently far such that the first fraction <NUM> of the application has passed the first boundary <NUM> of the transition zone <NUM>. In response, a hint image is displayed on the first display, indicating that the application will move to the first display upon release. <FIG> shows that the application has been moved so that a second, larger fraction <NUM> of the application, as defined from a left edge of the application to example line B, passes the first boundary <NUM> of the transition zone <NUM>, and in response a hint image is displayed spanning both displays, indicating that the application will span across both displays upon release. <FIG> shows that the application has been moved so that the second, larger fraction <NUM> of the application passes a second boundary <NUM> of the transition zone <NUM>, and in response a hint image is displayed on the first display, indicating that the application will move to the first display upon release. As such, there may be more than one predetermined area to which an application may be moved to trigger a same action.

<FIG> shows an example hint image displayed in response to a touch input moving an application to a display currently occupied by another application. In this example, a touch input moves the application from the second display toward the first display, but the first display is already occupied by another application. Upon dragging the application a certain threshold distance (such as those shown in <FIG> and <FIG>) or to a certain predetermined area, the other application on the left may slightly shrink and become greyed out as a hint image indicating that the dragged application would stack on top of the other application upon release and potentially cause the other application to close in some examples.

<FIG> shows an example hint image displayed in response to a touch input to swap applications. Here, the application has been dragged such that the first portion <NUM> of the application has passed an example swapping threshold line labeled as line C. Alternatively, the application may be dragged such that a far edge <NUM> of the application passes the first boundary <NUM> into the transition zone <NUM>. In response to either occurrence, a hint image is displayed showing the second application on the left at a smaller scale, and further showing the second application as a greyed out image on the second display, indicating that the application on the right will swap with the application on the left upon release. It will be understood that in some examples, hint images may not be displayed, but the same actions upon release within the predetermined areas may be applied regardless of whether hint images are displayed. Further, other suitable hint images may be used in other examples.

As mentioned above, in some examples, when a first application is moved from a first display to a second display that is already occupied by a second application, the first application is stacked on top of the second application. In some such examples, the second application may remain behind the first application indefinitely in a suspended state, until the first application is either moved away or dismissed. In other such examples, the second application may be dismissed automatically. In yet other examples, the second application may remain stacked behind the first application for a predetermined threshold amount of time, after which the second application may be dismissed and may then be accessible from a recent applications list. Within that threshold amount of time, a user may undo the stacking in order to reveal and resume the second application again. <FIG> shows an example user interface while stacking an application and then unstacking the application within a threshold time. At <NUM>, Application <NUM> is on the left display, and Application <NUM> is on the right display. At <NUM>, a touch input moves Application <NUM> toward the left display onto Application <NUM>, and Application <NUM> is shown smaller and transparent, as an example hint image indicating the stacking and possible application dismissal At <NUM>, Application <NUM> has been stacked on top of Application <NUM>. However, before a threshold amount of time has passed, a touch input moves Application <NUM> back toward the right display, as shown at <NUM>, thereby revealing Application <NUM> before it is dismissed. After the threshold amount of time, the dismissed application may be resumed again from a recent applications list, for example. Any suitable threshold time may be used. In some examples, the threshold time may be between five and twenty seconds, and may be ten seconds in a more specific example. Further, in some examples, an application that has become stacked underneath another application may instead (either immediately or after a predetermined threshold of time) be automatically transferred to a recent applications list for retrieval by the user.

In some examples, a user may trigger the launch of a new application from a currently open application, or a new instance of the same application. When in double portrait or double landscape mode, the new task may automatically be launched from the first application for display on the display opposite the first application, if that display is unoccupied.

In some instances, the user may attempt to launch a new task from a currently opened application when the opposite display is already occupied. <FIG> shows an example user interface depicting launching a new task from a link in an application while another application is open on another display. At <NUM>, the left display is occupied by Application <NUM> which contains a link, and the right display is occupied by Application <NUM>. At <NUM>, the user clicks on the link, which launches a new application, Application <NUM>. Because the adjacent display is occupied, the new Application <NUM> opens on the same display as Application <NUM>, stacking over Application <NUM> and suspending Application <NUM>, as shown at <NUM>. Application <NUM> may be displayed as if it is receding and/or shrinking as Application <NUM> launches and expands to cover the left display. At <NUM>, Application <NUM> has been stacked on top of Application <NUM>. In this instance, the stacking may not result in the automatic dismissal of Application <NUM>. Application <NUM> may be restored, for example, by user retrieval from a recent applications list, as mentioned above, or by a user touch input dismissing or moving Application <NUM> to the adjacent display.

Similarly, moving and spanning applications may behave differently depending on whether the display(s) are already occupied. <FIG> show various examples of spanning, stacking, swapping, and dismissal of applications in response to movements of one application when one or more display(s) are already occupied by one or more other applications. <FIG> shows an example user interface depicting spanning of an application over another application and then contracting of the spanned application, thereby restoring the application beneath the spanned application. At <NUM>, Application <NUM> is displayed on the first display, and Application <NUM> is displayed on the second display. At <NUM>, a user touch input moves Application <NUM> toward the seam, and releases to span Application <NUM> across both displays, stacking Application <NUM> over Application <NUM> on the second display, as shown at <NUM>. At <NUM>, a user touch input contracts Application <NUM> and moves Application <NUM> back to the first display. At <NUM>, Application <NUM> is revealed and restored.

<FIG> shows spanning and contracting an application when another application is open on another display, and also shows different outcomes as a result of contracting Application <NUM> to different screens. At <NUM>, Application <NUM> is displayed on the first display, and Application <NUM> is displayed on the second display. At <NUM>, Application <NUM> is shown spanned across both displays, e.g. after a touch input dragging and releasing Application <NUM> near the seam, thereby stacking at least a portion of Application <NUM> over Application <NUM> on the second display. The user may contract Application <NUM> back toward the first display, restoring Application <NUM> on the second display, as shown at <NUM>. Alternatively, the user may contract Application <NUM> toward the second display. Rather than stacking Application <NUM> over Application <NUM>, Application <NUM> may be automatically swapped with Application <NUM>, such that Application <NUM> is displayed on the first display, as shown at <NUM>. In other examples, swapping may be triggered when contracting a spanned application by moving the spanned application to a "swap threshold area" within an outer edge of the display, e.g. as illustrated in <FIG>. If the contracted application is released outside of the swap threshold area, it may result in permanent stacking.

<FIG> shows spanning and contracting of an application when two other applications are stacked on another display. At <NUM>, Application <NUM> is displayed on the first display, and Application <NUM> is displayed on the second display while stacked over Application <NUM>. At <NUM>, a user touch input moves Application toward the seam, and upon release, Application <NUM> spans across both displays, stacking over both Application <NUM> and Application <NUM> on the second display, as shown at <NUM>. At <NUM>, a user input contracts spanned Application <NUM>, but depending on which side Application <NUM> is contracted to, the result is different. At <NUM>, Application <NUM> is shown contracted to the first display, restoring the original arrangement. However, as shown at <NUM>, when the spanned application is contracted at the second display where the stacked applications were originally located, the stacked applications swap locations with the spanned application. As mentioned above, in other examples, swapping may be triggered when contracting the spanned application to a "swap threshold area" within an outer edge of the display, and stacking may result when the spanned application is released outside of the swap threshold area.

<FIG> shows spanning and contracting an application when a second application is stacked behind the application, and a third application is open on another display. At <NUM>, Application <NUM> is stacked over Application <NUM> on the first display, and Application <NUM> is displayed on the second display. At <NUM>, a user touch input moves Application <NUM> toward the seam. Application <NUM> is thereby spanned across both displays, stacking over both Application <NUM> on the first display and Application <NUM> on the second display, as shown at <NUM>. When the spanned application is contracted, at <NUM>, the application may stack above either the second application or the third application, depending to which side the application is contracted. At <NUM>, Application <NUM> is contracted to the first display, restoring Application <NUM> on the second display. At <NUM>, Application <NUM> is contracted to the second display, revealing Application <NUM> on the first display while Application <NUM> is stacked over Application <NUM> on the second display.

<FIG> shows spanning and contracting an application when a second application is stacked behind the application, and two other applications are stacked on another display. At <NUM>, Application <NUM> is stacked over Application <NUM> on the first display, and Application <NUM> is stacked over Application <NUM> on the second display. At <NUM>, a user touch input moves Application <NUM> toward the seam. When Application <NUM> is spanned, as shown at <NUM>, Application <NUM> remains stacked over Application <NUM> on the left display, and further stacks over Application <NUM> and Application <NUM> on the right display. A user touch input then contracts Application <NUM>, at <NUM>. When the user contracts Application <NUM> back to the left display, at <NUM>, Application <NUM> stacks back over Application <NUM> on the left display, while Application <NUM> and Application <NUM> remain stacked on the right display. In contrast, when the user contracts Application <NUM> on the right display, as shown at <NUM>, Application <NUM> stacks over Application <NUM>, dismissing Application <NUM>. This may occur, for example, if a setting dictates that only two applications may be stacked on a display at any time (other than when spanning). In other examples, more than two applications may be stacked at a time per display.

<FIG> shows an example method <NUM> of operating a dual screen computing device. Method <NUM> comprises, at <NUM>, displaying a first application a first display, and at <NUM>, displaying a second application at a second display of the dual screen computing device. Method <NUM> further includes, at <NUM>, receiving a touch input at the first display opening a third application while the first application is displayed on the first display, e.g. from a link within the first application. At <NUM>, method <NUM> comprises displaying the third application as being stacked over the first application. At <NUM>, method <NUM> includes receiving a touch input closing the third application, and in response, closing the third application and displaying the first application on the first display. The computing device may open new applications from currently running applications based on whether any application(s) are already open on either of the first display or the second display.

<FIG> shows another example method <NUM> of operating a dual-screen computing device, and more particularly illustrate various methods of displaying an application based upon the application being moved to different predetermined areas of the displays. Method <NUM> includes, at <NUM>, receiving a touch input at the first display dragging the first application from the first display toward the second display. In some examples, this may include receiving the touch input at an application navigation bar (e.g. displayed at a bottom, side, or other suitable location on the display, as illustrated in <FIG>). While the first application is being dragged, a size of the first application may be scaled based at least in part on a direction of movement of the touch input, at <NUM>. At <NUM>, method <NUM> includes displaying a hint indicating where the application will move based at least in part on the touch input dragging the first application to within a predetermined area. For example, hint images indicating that the first application will be spanned, moved, swapped, or stacked may be displayed indicating a result of the movement of the first application based on the touch input dragging the first application if the touch input is completed.

From <NUM>, method <NUM> may continue to <NUM> of <FIG>, or to <FIG>, <FIG>, which illustrate different outcomes depending on where the first application is released.

For example, method <NUM> may include, at <NUM>, detecting a touch input releasing the first application within a first predetermined area. This may include, at <NUM>, detecting the touch input releasing the first application within a threshold distance of a seam of the computing device in a hinge region of the device. In other examples, such a seam may not be present. At <NUM>, method <NUM> includes spanning the application across the first display and the second display, such that a portion of application content is hidden behind the seam. Spanning may include, at <NUM>, applying a mask to a rendering of the first application in a location corresponding to a seam in between the first display and the second display. In other examples, an image of the first application may be divided such that the full image is split between the two displays.

Further, spanning may include, at <NUM>, stacking a portion of the spanned, first application over a second application on the second display, where a second application is open on the second display.

Continuing with <FIG>, method <NUM> further includes, at <NUM>, receiving a touch input moving the spanned first application. Method <NUM> also includes, at <NUM>, moving the spanned application in a direction of the touch input to reveal at least a portion of the application content hidden behind the seam. Further, method <NUM> includes, at <NUM>, receiving a touch input moving and contracting the spanned application to either one of the first display and the second display, and displaying the first application on one of the first display and the second display based on the touch input. For example, a drag-and-release touch input or a fling gesture may contract the first application toward the first display, and the first application may be moved to the first display in response. In instances where the first application was stacked over the second application, moving the first application may reveal the second application, as indicated at <NUM>. As another example, the touch input may contract the first application onto the second display, such that the first application remains stacked over the second application, as shown at <NUM>, thereby potentially leading to the closing of the second application in some examples, e.g. immediately or after a threshold amount of time. As yet another example, the touch input may contract the first application onto the second display, such that the first application swaps positions with the second application, instead of stacking on top of the second application, as indicated at <NUM>.

Where the touch input is released in a different area than the first predefined area, a different result may occur than spanning. For example, <FIG> shows, at <NUM>, detecting the touch input releasing the first application within a second predefined area. In response, as indicated at <NUM>, the first application is moved to the second display, instead of being spanned across both displays. Such an action also may result from a fling gesture in which a touch input is moved from one of the first and second display toward the other of the first and second display with a velocity greater than a threshold velocity, and/or an acceleration greater than a threshold acceleration, also as indicated at <NUM>. Moving the first application to the second display may include, at <NUM>, stacking the first application over a second application on the second display. In some examples, the computing device may close the second application after a threshold amount of time of the first application being stacked over the second application, as shown at <NUM>. This may allow a user to move the stacked first application back to the first display to reveal the second application on the second display before the second application is closed. Thus, method <NUM> further includes, at <NUM>, receiving a touch input moving the first application back to the first display, and in response, displaying the first application on the first display. Where the first application was stacked over a second application and moved within a threshold amount of time, this also may include displaying the second application on the second display.

In another example response to the touch input received at <NUM>, <FIG> shows, at <NUM>, detecting the touch input releasing the first application within a third predefined area, and swapping the first application on the first display with the second application on the second display. As yet another example response to the touch gesture of <NUM>, <FIG> shows, at <NUM>, detecting the touch input releasing the first application within a fourth predefined area, and closing the first application in response. The touch input may drag-and-release the first application in any other suitable predetermined areas to trigger other corresponding actions, such as moving an application to a recent applications list, etc..

<FIG> shows an example user interface depicting interactions with an applications folder in a double portrait mode of the dual-screen device <NUM>. At <NUM>, the user interface shows a pinned applications bar <NUM> on the first display <NUM> of the first portion <NUM>, and a pinned applications bar <NUM> on the second display <NUM> of the first portion <NUM>. The user interface at <NUM> also shows a touch input <NUM> tapping an applications folder <NUM> on the first display <NUM> display. At <NUM>, the applications folder <NUM> is opened on the first display <NUM>. The open applications folder <NUM> may be at least partially transparent, such that content behind it is still visible. Further, the pinned applications that were on the pinned applications bar <NUM> on the first display <NUM> are shifted over to the pinned applications bar <NUM> on the second display <NUM>. In some examples, the shifting may be animated so that a user views the transition of the pinned applications to the other display. It will be understood that shifting of the pinned applications may occur in any instance where an application or system component (e.g. a folder) occupies either screen in a dual-display mode. At <NUM>, a touch input <NUM> performed on the second display <NUM> drags from left to right on the second display <NUM>, which moves the items displayed behind the applications folder <NUM> on the first display <NUM> to the second display <NUM>. At any time, a user may close the applications folder <NUM>, e.g. by tapping an "X" icon shown in the folder.

Continuing with <FIG>, at <NUM>, the applications folder <NUM> is opened on the second display <NUM>, such as after a touch input has moved the applications folder from the first display <NUM> to the second display <NUM>, or after touch inputs have closed the applications folder <NUM> on the first display <NUM>, and reopened the applications folder <NUM> on the second display <NUM>. The pinned applications that were previously on the pinned applications bar <NUM> of the second display <NUM> are shifted to the pinned applications bar <NUM> on the first display <NUM>. Similarly, a touch input <NUM> may be performed from right to left to shift content behind the applications folder <NUM> on the second display <NUM> to the first display <NUM>, as shown similarly at <NUM>. At <NUM>, while the applications folder <NUM> is open, a touch input <NUM> may move an application <NUM> that is not currently in the applications folder <NUM> into the folder <NUM>. It will be understood that pinned applications may also shift in response to the opening of an application on one display, and is not limited to the opening of an applications folder. Such behavior may allow the pinned applications to remain visible to a user.

In some examples, when no application or system component (e.g., folder) is open on either first display <NUM> or second display <NUM>, a user may also shift the pinned applications that were on pinned applications bar <NUM> on the first display <NUM> over to the pinned applications bar <NUM> on the second display <NUM> through a right swipe/fling gesture, either within the pinned applications bar <NUM> or a threshold area of pinned applications bar <NUM>. Similarly, the user may perform a left swipe/fling gesture either on pinned applications bar <NUM> or pinned applications bar <NUM> to shift the pinned applications that were previously on pinned applications bar <NUM> on the second display <NUM> over to pinned applications bar <NUM> on the first display <NUM>. This gives the user the control to launch whichever pinned application on the preferred display. It will be understood that the above examples, including any other windowing gestures described above, also apply to double landscape poses as well, and the described gesture directions are relative.

<FIG> shows an example method <NUM> of operating a dual screen computing device. Method <NUM> includes, at <NUM>, displaying one or more applications in a pinned applications bar on each of the first display and the second display. Method <NUM> further includes, at <NUM>, receiving a touch input opening an application or folder on one of the first display and the second display. In response, method <NUM> includes, at <NUM>, displaying the opened application or folder on the one of the first display and the second display, and shifting pinned applications on the one of the first display and second display to the other of the first display and the second display. For example, if a touch input opens an application on the first display, the pinned applications in the pinned applications bar on the first display may shift to the pinned applications bar of the second display. Likewise, if a touch input opens an application on the second display, the pinned applications in the pinned applications bar on the second display may shift to the pinned applications bar of the first display. It will be understood that this may also apply when opening an applications folder, as described in regard to <FIG>.

It will be understood that the various user interface examples described herein may apply to any suitable multiple display systems, including displays systems other than mobile phones, such as multi-monitor display systems for desktop computers, surface-mounted multi-displays, virtual and/or augmented reality display systems, head-up displays, projected display systems, etc. Furthermore, although described above in the context of touch inputs, it will be understood that any of the above touch inputs and gestures may also be input via a suitable input device, e.g. a mouse controlling a cursor.

Computing system <NUM> may embody the computer device <NUM> described above and illustrated in <FIG>. Computing system <NUM> may take the form of one or more personal computers, server computers, tablet computers, home-entertainment computers, network computing devices, gaming devices, mobile computing devices, mobile communication devices (e.g., smart phone), and/or other computing devices, and wearable computing devices such as smart wristwatches and head mounted augmented reality devices.

Computing system <NUM> includes a logic device <NUM>, and a non-volatile storage device <NUM>.

Logic device <NUM> includes one or more physical devices configured to execute instructions. For example, the logic device <NUM> may be configured to execute instructions that are part of one or more applications, programs, routines, libraries, objects, components, data structures, or other logical constructs.

The logic device <NUM> may include one or more physical processors (hardware) configured to execute software instructions. Additionally or alternatively, the logic device <NUM> may include one or more hardware logic circuits or firmware devices configured to execute hardware-implemented logic or firmware instructions. Processors of the logic device <NUM> may be single-core or multi-core, and the instructions executed thereon may be configured for sequential, parallel, and/or distributed processing. Individual components of the logic device <NUM> optionally may be distributed among two or more separate devices, which may be remotely located and/or configured for coordinated processing. Aspects of the logic device <NUM> may be virtualized and executed by remotely accessible, networked computing devices configured in a cloud-computing configuration.

Storage device <NUM> may be a non-volatile storage device. Non-volatile storage device <NUM> includes one or more physical devices configured to hold instructions executable by the logic device <NUM> to implement the methods and processes described herein.

It will be appreciated that storage device <NUM> is configured to hold instructions even when power is cut to the storage device <NUM>.

In other examples, storage device <NUM> may include volatile memory, which may include physical devices that include random access memory. Volatile memory is typically utilized by logic device <NUM> to temporarily store information during processing of software instructions. It will be appreciated that volatile memory typically does not continue to store instructions when power is cut to the volatile memory.

Aspects of logic device <NUM> and/or storage device <NUM> may be integrated together into one or more hardware-logic components.

When included, display subsystem <NUM> may be used to present a visual representation of data held by storage device <NUM>. Such display devices may be combined with logic device <NUM>, volatile memory and/or non-volatile storage device <NUM> in a shared enclosure, or such display devices may be peripheral display devices.

Another example provides a computing device, comprising a first portion comprising a first display and a first touch sensor, and a second portion comprising a second display and a second touch sensor, the second portion connected to the first portion via a hinge, the hinge defining a seam between the first display and the second display, the computing device further includes a logic device, and a storage device holding instructions executable by the logic device to receive a touch input at the first display moving an application that is currently displayed on the first display and not on the second display toward the second display, detect the touch input releasing the application within a predetermined area, span the application across the first display and the second display such that a portion of application content is hidden behind the seam, receive a touch input moving the spanned application, and move the spanned application in a direction of the touch input moving the spanned application to reveal at least a portion of the application content hidden behind the seam. The instructions may be additionally or alternatively executable to span the application across the first display and the second display by applying a mask to a rendering of the displayed application in a location corresponding to the seam. The instructions may be additionally or alternatively executable to receive a touch input moving the spanned application to one of the first display and the second display, and display the spanned application on one of the first display and the second display. The instructions may be additionally or alternatively executable to display one or more applications in a pinned applications bar on each of the first display and the second display, receive a touch input opening an applications folder on one of the first display and the second display, and in response, display the applications folder on the one of the first display and the second display, and shift applications on the one of the first display and the second display to the other of the first display and the second display. The predefined area may be a first predefined area, and the instructions may be additionally or alternatively executable to detect a touch input moving the application toward the second display and releasing the application within a second predefined area, and move the application to the second display. The application may be a first application, and the instructions may be additionally or alternatively executable to display a second application on the second display, upon detecting the touch input releasing the application within the second predefined area, stack the first application over the second application on the second display. The instructions may be additionally or alternatively executable to close the second application after a threshold amount of time of the first application being stacked over the second application. The application may be a first application, and the instructions may be additionally or alternatively executable to display a second application on the second display, detect a touch input releasing the application within a second predefined area, and swap the first application on the first display with the second application on the second display. The application may be a first application, and the instructions may be additionally or alternatively executable to display a second application on the second display, wherein spanning the first application across the first display and the second display comprises stacking a portion of the first application over the second application on the second display, receive a touch input contracting the first application, and display the first application on the first display, and display the second application on the second display. The predefined area may be a first predefined area, and the instructions may be additionally or alternatively executable to detect a touch input releasing the application within a second predefined area, and close the application. The instructions may be additionally or alternatively executable to detect a touch input comprising a fling gesture, and move the application to the second display. The instructions may be additionally or alternatively executable to scale a size of the application based at least in part on a direction of movement of the touch input. The instructions may be additionally or alternatively executable to, prior to detecting the touch input releasing the application, display a hint indicating that the application will span based at least in part on the touch input moving the application to within the predetermined area.

Another example provides a computing device, comprising a first portion comprising a first display and a first touch sensor, a second portion comprising a second display and a second touch sensor, the second portion connected to the first portion via a hinge, the hinge defining a seam between the first display and the second display, a logic device, and a storage device holding instructions executable by the logic machine to receive a touch input at the first display moving an application from the first display toward the second display, when the touch input releases the application within a first predefined area, move the application to the second display, and when the touch input releases the application within a second predetermined area, span the application by displaying the application across the first display and the second display. The application may be a first application, and the instructions may be additionally or alternatively executable to, display a second application on the second display, and when the user input releases the first application in a third predefined area, swap the first application on the first display with the second application on the second display by displaying the first application on the second display and displaying the second application on the first display. The application may be a first application, and the instructions may be additionally or alternatively executable to, display a second application on the second display, when the first application is displayed on the first display, receive a touch input at the first display opening a third application from the first application, and display the third application as being stacked over the first application. The instructions may be additionally or alternatively executable to receive a touch input closing the third application, and displaying the first application on the first display.

Another example provides a method enacted on a computing device, the computing device comprising a first portion comprising a first display and a first touch sensor, and a second portion comprising a second display and a second touch sensor, the second portion connected to the first portion via a hinge, the hinge defining a seam between the first display and the second display, the method comprising displaying a first application on the first display, displaying a second application on the second display, receiving a touch input at the first display moving the first application toward the second display, detecting the touch input releasing the application within a predetermined area, and stacking the first application over the second application on the second display based at least upon the touch input releasing the application within the predetermined area. The method may additionally or alternatively include receiving a touch input moving the first application to the first display, and in response, displaying the first application on the first display and displaying the second application on the second display. The method may additionally or alternatively include closing the second application after a threshold amount of time of the first application being stacked over the second application.

Claim 1:
A computing device (<NUM>), comprising:
a first portion (<NUM>) comprising a first display (<NUM>) and a first touch sensor;
a second portion (<NUM>) comprising a second display (<NUM>) and a second touch sensor, the second portion connected to the first portion via a hinge (<NUM>);
a logic device (<NUM>); and
a storage device (<NUM>) holding instructions executable by the logic device to:
receive (<NUM>) a touch input at the first display moving an application that is currently displayed on the first display and not on the second display toward the second display,
based at least upon the touch input releasing the application within a first predefined area, move the application to the second display, wherein if the application is moved from the first display to the second display and the second display is already occupied by a second application, the instructions are further executable to stack the application on top of the second application,
based at least upon the touch input releasing the application within a second predefined area different than the first predefined area, span the application across the first display and the second display, and
based at least upon the touch input releasing the application within a third predefined area and the second display currently displaying the second application, swap the application on the first display with the second application on the second display.