Operation Window for Portable Devices with Touchscreen Displays

Novel tools and techniques are described for invoking and subsequently hiding or minimizing an operation window within a portion of a display area of a touchscreen display of a mobile device. The operation window may be invoked and hidden/minimized using default, preset, or customizable user inputs. The operation window, whose position, size, and content display options may be customizable by a user, allows a user to easily and comfortably interact with, operate, and/or navigate, using only one hand, software applications (e.g., user interfaces) running on a mobile device and displayed on the touchscreen display of the mobile device. This particular functionality is especially applicable to mobile devices having relatively large touchscreen displays that require two hands to comfortably operate while holding the mobile device.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

Hereinafter, the term, “operation window” refers to a display window displayed within a display area of the touchscreen display that is smaller in size than the touchscreen display area, and that represents information (e.g., an interactive software or applications user interface, multimedia content, and/or a combination of the two) displayed on a main screen window or main screen display (either as a miniature version thereof, or a reformatted and resized representation of the displayed content thereof). Accordingly, “main screen window” or “main screen display” refers to a display window that normally fills the touchscreen display area or a substantial portion thereof, and that is intended for normal operation of the mobile device. As is well understood in the art, “hiding” of a window refers to either hiding the subject window behind another display window or minimizing the subject window so that it is not displayed on the touchscreen display. As is also well understood in the art, the size of a screen of a mobile device is measured from one corner of a display area of the screen to an opposite corner of the display area (e.g., from a lower-left-hand corner to an upper-right-hand corner or from a lower-right-hand corner to an upper-right-hand corner). For example, a 4.5 inch (11.43 cm) display screen of a mobile phone is measured from one of a lower-left-hand corner to an upper-right-hand corner and from a lower-right-hand corner to an upper-right-hand corner of the display area of the mobile phone's display screen. In this disclosure, the terms, “hand swipe,” “finger swipe,” and “thumb swipe” (or similar phrases) are interchangeable, and refer to a user using his hand, finger, thumb, or stylus to interact with the touchscreen display to cause the software applications running on the mobile device to perform a particular task.

With reference to the figures,FIG. 1is a generalized diagram illustrating a prior art mobile device100. InFIG. 1, a prior art mobile device100includes a touchscreen display105and various hard or soft buttons110. Touchscreen display105displays a main screen window that is sized to fill a substantial or entire display area of touchscreen display105. In some mobile devices, such as smart phones (e.g., Google® Androie®-based mobile phones, like the Samsung® Galaxy S 3™ or Samsung® Galaxy S 4™, or Apple Inc.-based mobile phones, like the Apple™ iPhone 5™), the main screen window is divided into a plurality of screen panels. In such a case, one of the plurality of screen panels may be configured to fill the substantial or entire display area at any one time. As discussed above, as the size of the touchscreen display increases in subsequent models of smart phones, with screen sizes exceeding, e.g., 3.5 inches (˜8.89 cm), which is generally thought to be a comfortable size for a user to operate a touchscreen display with one hand, it becomes increasing more difficult for users to operate or navigate functions on their smart phones and other touchscreen mobile devices (e.g., tablet computers, PDAs, e-book readers, etc.) with a single hand. This problem is addressed in various embodiments as discussed below with respect toFIGS. 2A-5.

Referring toFIGS. 2A-2C(collectively, “FIG.2”),FIGS. 2A-2Care generalized diagrams illustrating a mobile device200configured to allow a user to operate the touchscreen display205using one hand, by invoking an operation window220, in accordance with various embodiments. InFIG. 2A, mobile device200includes a touchscreen display205and various hard or soft buttons210. Touchscreen display205displays a main screen window that is sized to fill the substantial or entire display area of touchscreen display205. In order to allow a user to navigate or operate functions displayed on the touchscreen display205using only one hand, particularly with display areas that are larger than ˜3.5 inches (˜8.89 cm), mobile device200is configured (e.g., by configuring the operating system of the mobile device200or by configuring a mobile device application (“app”) downloaded and installed on the mobile device) to allow the user to invoke an operation window220by, e.g., recognizing and receiving a user input215.

According to some embodiments, user input215may include any customizable or preset inputs that are associated with the function of invoking operation window220. For example, for a right-handed user, user input215may include a hand swipe that begins generally near the vicinity of the lower-right-hand corner of the display area toward the middle of the display area or toward the upper-left-hand corner of the display area. Such a diagonal hand swipe avoids conflicts with other hand swipe-operated functions such as horizontal left/right hand swipes that may already be associated with changing between a plurality of panels in a smart phone or vertical up/down hand swipes that may already be associated with viewing/closing status screens or viewing/closing menu/option screens. For a left-handed user, user input215may include a hand swipe that begins generally near the vicinity of the lower-left-hand corner of the display area toward the middle of the display area or toward the upper-right-hand corner of the display area. According to some embodiments, user input215may include user selection of an option selectable from a pop-up menu to invoke the operation window220.

Turning toFIG. 2B, upon receiving user input215, the mobile device200(or the processor therein) is configured to invoke and display on the touchscreen display205an operation window220. Operation window220is configured to fill only a portion of the display area. Ideally, the size of the operation window220is configured to be large enough to clearly display the screen information on the main screen display, yet small enough to allow the user to operate (or navigate), using only a single hand, software applications (e.g., user interfaces, etc.) running on mobile device200and displayed on the touchscreen display205. In some embodiments, the size of operation window220does not exceed ˜3.5 inches (˜8.89 cm), which is generally thought to be the upper limit for comfortable operation or navigation of a touchscreen display device with one hand. In some embodiments, the user may be provided with options and/or the capability to change, customize, or preset the size of the operation window220. This may be done, e.g., by providing the user with access to user preferences that detail how the user would generally prefer to size the operation window. For example, this may be accomplished by allowing the user to press and hold down on a particular region of the operation window to invoke a menu screen that presents the user with options to resize the operation window220. Alternatively, the resizing operation may be accomplished by allowing the user to hold down on and drag a particular portion of the operation window220(including, but not limited to, one or more corners of the operation window220, or one or more of the top/bottom/side edges of the operation window220) so as to resize the operation window220.

According to some embodiments, the user may be provided with options and/or the capability to change, customize, or preset how content displayed on the operation window220will be resized and reformatted, or otherwise presented. This may be done, e.g., by providing the user with access to user preferences (which may be the same as those for resizing the operation window220) that detail how the user would generally prefer the content of the operation window to be resized, reformatted, or otherwise presented in the operation window220. Alternatively, the resizing/reformatting operation may be accomplished by allowing the user to press and hold on a particular region of the operation window to invoke a menu screen that presents the user with options to resize, reformat, or otherwise present the content on the operation window220. In some embodiments, if no customized configuration is available or otherwise provided by the user, the default operation window displays the exact same image as the main display area, but in smaller dimensions. In accordance with some embodiments, content display options include options selected from a group consisting of resizing the content while locking an aspect ratio of the content, reformatting font and content sizes to fit a size and shape of the operation window based on predetermined criteria, and rearranging icons or multimedia content in the operation window to fit the size and shape of the operation window based on predetermined criteria. Predetermined criteria may include default or user preset criteria that designate rules for how to reformat the font and content based on ranges of sizes of the operation window and based on the shapes of the operation window. Predetermined criteria may also include default or user preset criteria that designate rules for how to rearrange icons or multimedia content based on ranges of sizes of the operation window and based on the shapes of the operation window.

As shown inFIG. 2B, the operation window220is shown positioned generally at the lower-right-hand corner of the touchscreen display205. However, the operation window220may be positioned or repositioned anywhere within the display area of touchscreen display205. For example, for a left-handed user, positioning the operation window220generally at the lower-left-hand corner of the display area of touchscreen display205would be more appropriate and more comfortable for the left-handed user. Alternatively, the operation window220may be positioned along one of the top, bottom, right, or left sides, but not the corners, of the display area of the touchscreen display205, or generally at the upper-left-hand corner or the upper-right-hand corner of the display area of the touchscreen display205. In some embodiments, the operation window220may be displayed in a middle region of the display area, i.e., anywhere in the display area that is not abutting any of the top, bottom, right, or left sides of the display area, or any of the upper-left-hand, upper-right-hand, lower-left-hand, or lower-right-hand corners of the display area.

According to some embodiments, the user may be provided with options and/or the capability to change, customize, or preset the position of the operation window220to be displayed or that is displayed in the display area of touchscreen display205. This may be done, e.g., by providing the user with access to user preferences (which may be the same as those for resizing the operation window220and for resizing, reformatting, or otherwise presenting content in the operation window220) that detail how the user would generally prefer to position the operation window220. Alternatively, the position/reposition of the operation window220may be accomplished by allowing the user to press and hold on a particular region of the operation window to invoke a menu screen that presents the user with options to position or reposition the operation window220. In some embodiments, the positioning/repositioning operation may be performed by allowing the user to hold down on and drag a particular portion of the operation window220(including, but not limited to, one or more corners of the operation window220, or one or more of the top/bottom/side edges of the operation window220, or a middle (i.e., non-edge, non-corner) portion of the operation window220) so as to reposition the operation window220to another part of the display area of touchscreen display205.

According to some embodiments, the main screen, whose content is presented on the operation window220(e.g., in a reformatted, resized, or otherwise presented form), may continue to be displayed in the background, underneath the operation window220. In some embodiments, any changes in the display of content in the operation window220may be projected, reflected, or otherwise displayed in the main screen display, which is in the background of the display, underneath the operation window220. In accordance with some embodiments, the projection, reflection, or display of any changes in the display of content in the operation window220onto the main screen display is either immediate (or instant) or may lag by a measurable processor delay time. In some alternative embodiments, the main screen display may be hidden and replaced with a customizable background (e.g., a preset or default or customized wallpaper, or a preset or default or customized screensaver, either or both of which may be static or dynamic), with the operation window220overlaid on the customizable background.

With reference toFIG. 2C, after the user has interacted with, operated, and/or navigated the software application (e.g., user interface) running on the mobile device200and displayed on the operation window220, and intends to return to the main screen display, the mobile device200(or the processor therein) is configured to allow the user to hide or minimize the operation window220, by recognizing and receiving a user input225. According to some embodiments, the user input225may include any customizable or preset inputs that are associated with the function of hiding or minimizing operation window220. For example, for a right-handed user, user input225may include a hand swipe that begins generally near the vicinity of the middle of the display area toward the lower-right-hand corner of the display area. As with the diagonal hand swipe for user input215, such a diagonal hand swipe for user input225avoids conflicts with other hand swipe-operated functions such as horizontal left/right hand swipes that may already be associated with changing between a plurality of panels in a smart phone or vertical up/down hand swipes that may already be associated with viewing/closing status screens or viewing/closing main screens. For a left-handed user, user input225may include a hand swipe that begins generally near the vicinity of the middle of the display area toward the lower-left-hand corner of the display area. According to some embodiments, user input225may include user selection of an option selectable from a pop-up menu to hide and/or minimize the operation window220.

In an exemplary embodiment, user input225may include a variation of the resizing operation as discussed above in relation toFIG. 2B. In such a resizing operation, if the user input225positions the operation window220so as to abut one of the four corners of the display area (in the case that the operation window220is positioned in the middle portion of the display area that is not abutting any of the four sides or four corners of the display area), and drags the corner of the operation window220that is in the middle of the display area from the middle region to one of the four corners of the display area (i.e., one of the upper-left-hand corner, the upper-right-hand corner, the lower-left-hand corner, and the lower-right-hand-corner of the display area) of touchscreen205, the mobile device200(or the processor therein) will either replace the main screen with the full-size operation window220(which becomes the new main screen), hide/minimize the operation window220and display the main screen, or simply overlap the full-size operation window220on top of the main screen.

With the operation window220hidden or minimized, the main screen may be revealed to fill the substantial or entire display area of the touchscreen display205. In the embodiments where the main screen is replaced with a static/dynamic screensaver or wallpaper, the operation for hiding or minimizing the operation window220may invoke or otherwise cause the display of the main screen so as to fill the substantial or entire display area of the touchscreen display205.

With reference toFIGS. 3A-3E(collectively, “FIG.3”),FIGS. 3A-3Eare generalized diagrams illustrating an example operation utilizing the mobile device200as shown inFIG. 2, in accordance with various embodiments. In particular,FIG. 3illustrates various embodiments in which the user desires to make a telephone call on a smart phone having a relatively large touchscreen display (i.e., a touchscreen display that exceeds, e.g., ˜3.5 inches (˜8.89 cm) in size). This operation is merely an example. Other operations that may benefit from the use of the operation window may include, but are not limited to, taking a photograph using the camera, recording a voice input using the microphone, browsing the Internet, inputting text into one or more text fields of a user interface, navigating using a user interface of a global positioning system (“GPS”) software app, entering inputs for interacting with gaming software or gaming apps, etc. The operation of invoking and hiding/minimizing the operation window220is as discussed above with respect toFIGS. 2A-2C.

InFIG. 3A, the main screen contains a telephone dialing screen, in which is displayed a calling or destination number display region230(hereinafter, “call display region230”), and soft buttons235representing the number pad including the ten different Arabic numbers from 0 through 9 as well as the pound (“#”) and star (“*”) keys (hereinafter, “number pad buttons235”). By entering user input215(e.g., a hand swipe from the lower-right-hand corner of the display area toward the middle or upper-left-hand corner of the display area; or a hand swipe from the lower-left-hand corner of the display area toward the middle or upper-right-hand corner of the display area), the user invokes operation window220(shown inFIG. 3B). As discussed above, user input215may include other inputs by the user other than the specific hand swipes mentioned that are associated with invoking the operation window220

Turning toFIG. 3B, invoking operation window220causes operation window220to be displayed overlaying the main screen. In this exemplary embodiment, the contents of the main screen are reformatted, resized, or otherwise presented in the operation window220, according to preset, default, or user customizable resizing, repositioning, and presentation options as discussed above in relation toFIG. 2B. As shown inFIG. 3B, for example, a default or preset (preference) setting may be for the operation window to be located generally at (or abutting) the lower-right-hand corner of the display area (although in some embodiments, the operation window220may be preset to be positioned generally at (or abutting) the lower-left-hand corner of the display area). InFIG. 3B, call display region230and number pad buttons235are resized and reformatted to fit the size of operation window220, and are subsequently displayed or otherwise presented in the operation window220as call display region240and number pad buttons245, respectively.

Referring toFIG. 3C, a right-handed user may input a telephone number using a finger of a single hand (i.e., his or her right thumb). For example, as shown inFIG. 3C, the user may enter the numbers “8,” “3,” and “2” using number pad buttons245. For a left-handed user, the operation window220would be positioned generally at (or abutting) the lower-left-hand corner of the display area to allow the left-handed person to more comfortably and/or more easily enter the telephone number with his or her left thumb.

According to some embodiments, the main screen may continue to be displayed in the background. In some embodiments, the numbers “8,” “3,” and “2” that are entered using number pad buttons245and displayed on call display region240may be projected, reflected, or otherwise displayed on the main screen in call display region230. The projection, reflection, or other display on call display region230of each of the numbers entered using the number pad buttons245may be performed roughly, almost simultaneously, approximately concurrently, or exactly concurrently with the display of each number on call display region240.

As shown inFIG. 3D, once the user has completed interacting, operating, and/or navigating the functions of the software application (e.g., user interface) displayed on the operation window220, the user may hide or minimize the operation window220by entering user input225(e.g., a hand swipe from the middle of the display area toward the lower-right-hand corner of the display area; or a hand swipe from the middle of the display area toward the lower-left-hand corner of the display area). As discussed above, user input225may include other inputs by the user other than the specific hand swipes mentioned that is associated with hiding or minimizing the operation window220.

Turning toFIG. 3E, upon receiving the user input225, the mobile device (or the processor therein) causes the processor to hide or minimize the operation window220, thus leaving the main screen to fill the substantial or entire display area of the touchscreen display205.

We turn now toFIG. 4.FIG. 4is a flow chart illustrating a method300for allowing a user to operate a touchscreen display or a mobile device using one hand, by invoking an operation window, in accordance with various embodiments. At block305, the method includes receiving a first input or a first set of inputs215from the user (including, but not limited to a diagonal hand swipe from either the lower-right-hand corner toward the middle or the upper-left-hand corner, a diagonal hand swipe from either the lower-left-hand corner toward the middle or the upper-right-hand corner, selecting to invoke the operation window220from a menu option, etc.). Upon receiving user input215, the method includes generating and displaying an operation window220on a portion of the display screen (at block310). In some embodiments, the operation window220may be overlaid on one of the main screen (the contents of which are reformatted, resized, or otherwise presented in the operation window220), a static/dynamic wallpaper, or a static/dynamic screensaver. At block315, a second input or a second set of inputs is received from the user for customizing the size and position of the operation window220. The second input or second set of inputs may also include options for customizing how the content from the main screen may be reformatted, resized, or otherwise displayed in the operation window220. The functionality at block315may be optional, as preset or default sizing, positioning, and content formatting options may be invoked if the user does not enter the second input or a second set of inputs within an predetermined time period (e.g., 1, 2, or 3 seconds) after invoking the operation window220at block305. Alternatively, the functionality at block315may be implemented any time after the operation window220has been invoked and displayed.

At block320, the input fields from the main screen are mapped onto the operation window220. In other words, due to the resizing (i.e., general miniaturizing) or reformatting (i.e., general or slight changing of the interactive icons, etc.), the input fields on the operation window220must be reconfigured so that the user who would normally touch a particular region on the main screen to cause a function to be performed can touch a particular region in the operation window220corresponding to said particular region on the main screen. With reference toFIGS. 3B-3D, for example, a user who intends to type the number “8” on the number pad button235, and who would normally touch the particular region of the main screen corresponding to the number pad button235for the number “8,” would instead touch the particular region of the operation window220corresponding to number pad button245corresponding to the number “8.” Accordingly, the input fields for the number pad button235for number “8” on the main screen must be mapped onto the number pad button245for number “8” on the operation window220, and so on.

Once the input mapping has been completed, the method receives a third input or a third set of inputs from the user for interacting with, operating, and/or navigating the software application that is displayed on the operation window220(at block325). In the embodiments in which the main screen continues to be displayed underneath the operation window220(i.e., in the background of the display), at block330, any changes displayed on the operation window220may be projected, reflected, or otherwise displayed on the main screen display that is in the background.

After the user has completed interacting with, operating, and/or navigating the software application (e.g., user interface) that is displayed in the operation window220, the method receives a fourth input or a fourth set of inputs225from the user (including, but not limited to a diagonal hand swipe from the middle toward the lower-right-hand corner, a diagonal hand swipe from the middle toward the lower-left-hand corner, selecting to hide or minimize the operation window220from a menu option, etc.) for hiding or minimizing the operation window220. At block340, upon receiving fourth input225, the operation window220is hidden or minimized.

Referring now toFIG. 5,FIG. 5is a block diagram illustrating hardware components within mobile device400, some of which are configured to allow a user to operate a touchscreen display or a mobile device using one hand, by invoking an operation window, in accordance with various embodiments. InFIG. 5, a block diagram of an exemplary mobile device400is shown that includes at least one of processor405, memory410, and touchscreen display415. Processor405may be configured to execute software, such as an operating system of the mobile device, to cause the mobile device400to invoke and display operation window220in a portion of the display area of touchscreen display415in response to receiving user input215. Any presets, defaults, or other settings for sizing/resizing, positioning/repositioning, formatting/reformatting, or otherwise presenting the operation window220and/or the content displayed therein within the display area of touchscreen display415may be stored in memory410. Memory410may include a RAM, a PROM, an EPROM, a FLASH-EPROM, or any other memory chip or cartridge, a carrier wave (e.g., electromagnetic signals, acoustic signals, optical signals, and/or the like), or any other medium from which a computer or a mobile device can read instructions and/or code.

According to some embodiments, mobile device400may further include at least one of network transceiver420, memory drive or slot425, camera430, or microphone435. In some embodiments, the network transceiver420may be used to update, over a wireless network connection, the software (e.g., operating system or mobile device application (“app”)) that allows the user to invoke/hide/minimize an operation window according to various embodiments discussed above. The various presets, defaults, or other settings for sizing/resizing, positioning/repositioning, formatting/reformatting, or otherwise presenting the operation window220and/or the content displayed therein within the display area of touchscreen display415may also be downloaded from a network (e.g., the Internet; a local area network (“LAN”), including without limitation a fiber network, an Ethernet network, a Token-Ring™ network and/or the like; a wide area network (“WAN”); a wireless wide area network (“WWAN”); a virtual network, such as a virtual private network (“VPN”); a personal area network (“PAN”); an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network, including without limitation a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth™ protocol known in the art, and/or any other wireless protocol; and/or any combination of these and/or other networks) over a wireless network connection via network transceiver420.

In some embodiments, the software (e.g., operating system or mobile device application (“app”)) and/or the presets, defaults, or other settings for sizing/resizing, positioning/repositioning, formatting/reformatting, or otherwise presenting the operation window220and/or the content displayed therein within the display area of touchscreen display415may be stored on, and transferred to the mobile device400via, an external memory device (e.g., a solid state memory drive, including, but not limited to, a secure digital (“SD”) card or micro SD card, a flash memory drive, etc.). In such a case, memory drive or slot425may be configured to receive and connect with corresponding contact points on the external memory device, for transferring the software and/or the presets, defaults, or other settings from the external memory device to the memory410.

According to some embodiments, camera430or microphone435(or the settings for either component) may be controlled using an operation window220that is invoked according to various embodiments discussed above.