Variable device graphical user interface

Methods, systems, devices, and apparatus, including computer program products, for adjusting a graphical user interface. A motion of a device is detected. A graphical user interface of the device is adjusted in response to the detected motion.

BACKGROUND

The subject matter of this specification relates generally to graphical user interfaces.

Some of today's portable devices include a touch-sensitive display. A graphical user interface can be displayed on the touch-sensitive display. A user of a device can interact with the graphical user interface by making contact with the touch-sensitive display. The device, being a portable device, can also be carried and used by a user while the user is in motion. While the user and the device is in motion, the user's dexterity with respect to the touch-sensitive display can be disrupted by the motion, detracting form the user's experience with the graphical user interface.

SUMMARY

In general, one aspect of the subject matter described in this specification can be embodied in methods that include the actions of detecting a pattern of motion of a device; and adjusting a graphical user interface of the device in response to the detected pattern of motion. Other embodiments of this aspect include corresponding systems, apparatus, devices, computer program products, and computer readable media.

In general, another aspect of the subject matter described in this specification can be embodied in methods that include the actions of detecting a motion of a device; comparing the detected motion to a predetermined signature of motion; and adjusting a graphical user interface of the device based on the comparing. Other embodiments of this aspect include corresponding systems, apparatus, devices, computer program products, and computer readable media.

Particular embodiments of the subject matter described in this specification can be implemented to realize one or more of the following advantages. Loss in accuracy of a user's interactions with a touch-sensitive display of a device or user mistakes with respect to the selection of user interface elements on a touch-sensitive display, due to movement of the user and/or the device, is mitigated. A device user interface can be adjusted to provide better visibility or usability.

DETAILED DESCRIPTION

Example Mobile Device

FIG. 1is a block diagram of an example mobile device100. The mobile device100can be, for example, a handheld computer, a personal digital assistant, a cellular telephone, a network appliance, a camera, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an email device, a game console, or a combination of any two or more of these data processing devices or other data processing devices.

Mobile Device Overview

In some implementations, the mobile device100includes a touch-sensitive display102. The touch-sensitive display102can implement liquid crystal display (LCD) technology, light emitting polymer display (LPD) technology, or some other display technology. The touch sensitive display102can be sensitive to haptic and/or tactile contact with a user.

In some implementations, the touch-sensitive display102can comprise a multi-touch-sensitive display102. A multi-touch-sensitive display102can, for example, process multiple simultaneous touch points, including processing data related to the pressure, degree, and/or position of each touch point. Such processing facilitates gestures and interactions with multiple fingers, chording, and other interactions. Other touch-sensitive display technologies can also be used, e.g., a display in which contact is made using a stylus or other pointing device. Some examples of multi-touch-sensitive display technology are described in U.S. Pat. Nos. 6,323,846, 6,570,557, 6,677,932, and 6,888,536, each of which is incorporated by reference herein in its entirety.

In some implementations, the mobile device100can display one or more graphical user interfaces on the touch-sensitive display102for providing the user access to various system objects and for conveying information to the user. In some implementations, the graphical user interface can include one or more display objects104,106. In the example shown, the display objects104,106, are graphic representations of system objects. Some examples of system objects include device functions, applications, windows, files, alerts, events, or other identifiable system objects.

Example Mobile Device Functionality

In some implementations, the mobile device100can implement multiple device functionalities, such as a telephony device, as indicated by a phone object110; an e-mail device, as indicated by the e-mail object112; a network data communication device, as indicated by the Web object114; a Wi-Fi base station device (not shown); and a media processing device, as indicated by the media player object116. In some implementations, particular display objects104, e.g., the phone object110, the e-mail object112, the Web object114, and the media player object116, can be displayed in a menu bar118. In some implementations, device functionalities can be accessed from a top-level graphical user interface, such as the graphical user interface illustrated inFIG. 1. Touching one of the objects110,112,114, or116can, for example, invoke corresponding functionality.

In some implementations, the mobile device100can implement network distribution functionality. For example, the functionality can enable the user to take the mobile device100and provide access to its associated network while traveling. In particular, the mobile device100can extend Internet access (e.g., Wi-Fi) to other wireless devices in the vicinity. For example, mobile device100can be configured as a base station for one or more devices. As such, mobile device100can grant or deny network access to other wireless devices.

In some implementations, upon invocation of device functionality, the graphical user interface of the mobile device100changes, or is augmented or replaced with another user interface or user interface elements, to facilitate user access to particular functions associated with the corresponding device functionality. For example, in response to a user touching the phone object110, the graphical user interface of the touch-sensitive display102may present display objects related to various phone functions; likewise, touching of the email object112may cause the graphical user interface to present display objects related to various e-mail functions; touching the Web object114may cause the graphical user interface to present display objects related to various Web-surfing functions; and touching the media player object116may cause the graphical user interface to present display objects related to various media processing functions.

In some implementations, the top-level graphical user interface environment or state ofFIG. 1can be restored by pressing a button120located near the bottom of the mobile device100. In some implementations, each corresponding device functionality may have corresponding “home” display objects displayed on the touch-sensitive display102, and the graphical user interface environment ofFIG. 1can be restored by pressing the “home” display object.

In some implementations, the top-level graphical user interface can include additional display objects106, such as a short messaging service (SMS) object130, a calendar object132, a photos object134, a camera object136, a calculator object138, a stocks object140, a weather object142, a maps object144, a notes object146, a clock object148, an address book object150, and a settings object152. Touching the SMS display object130can, for example, invoke an SMS messaging environment and supporting functionality; likewise, each selection of a display object132,134,136,138,140,142,144,146,148,150, and152can invoke a corresponding object environment and functionality.

Additional and/or different display objects can also be displayed in the graphical user interface ofFIG. 1. For example, if the device100is functioning as a base station for other devices, one or more “connection” objects may appear in the graphical user interface to indicate the connection. In some implementations, the display objects106can be configured by a user, e.g., a user may specify which display objects106are displayed, and/or may download additional applications or other software that provides other functionalities and corresponding display objects.

In some implementations, the mobile device100can include one or more input/output (I/O) devices and/or sensor devices. For example, a speaker160and a microphone162can be included to facilitate voice-enabled functionalities, such as phone and voice mail functions. In some implementations, an up/down button184for volume control of the speaker160and the microphone162can be included. The mobile device100can also include an on/off button182for a ring indicator of incoming phone calls. In some implementations, a loud speaker164can be included to facilitate hands-free voice functionalities, such as speaker phone functions. An audio jack166can also be included for use of headphones and/or a microphone.

In some implementations, a proximity sensor168can be included to facilitate the detection of the user positioning the mobile device100proximate to the user's ear and, in response, to disengage the touch-sensitive display102to prevent accidental function invocations. In some implementations, the touch-sensitive display102can be turned off to conserve additional power when the mobile device100is proximate to the user's ear.

Other sensors can also be used. For example, in some implementations, an ambient light sensor170can be utilized to facilitate adjusting the brightness of the touch-sensitive display102. In some implementations, an accelerometer172can be utilized to detect movement of the mobile device100, as indicated by the directional arrow174. Accordingly, display objects and/or media can be presented according to a detected orientation, e.g., portrait or landscape. In some implementations, the mobile device100includes circuitry and sensors for supporting a location determining capability, such as that provided by the global positioning system (GPS) or other positioning systems (e.g., systems using Wi-Fi access points, television signals, cellular grids, Uniform Resource Locators (URLs)). In some implementations, a positioning system (e.g., a GPS receiver) can be integrated into the mobile device100or provided as a separate device that can be coupled to the mobile device100through an interface (e.g., port device190) to provide access to location-based services. In some implementations, the mobile device100includes a gyroscopic sensor or other sensors that can be used to detect motion of the device.

In some implementations, a port device190, e.g., a Universal Serial Bus (USB) port, or a docking port, or some other wired port connection, can be included. The port device190can, for example, be utilized to establish a wired connection to other computing devices, such as other communication devices100, network access devices, a personal computer, a printer, a display screen, or other processing devices capable of receiving and/or transmitting data. In some implementations, the port device190allows the mobile device100to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP, HTTP, UDP and any other known protocol. In some implementations, a TCP/IP over USB protocol can be used, as described in U.S. Provisional Patent Application No. 60/945,904, filed Jun. 22, 2007, for “Multiplexed Data Stream Protocol,” which provisional patent application is incorporated by reference herein in its entirety.

The mobile device100can also include a camera lens and sensor180. In some implementations, the camera lens and sensor180can be located on the back surface of the mobile device100. The camera can capture still images and/or video.

The mobile device100can also include one or more wireless communication subsystems, such as an 802.11b/g communication device186, and/or a Bluetooth™ communication device188. Other communication protocols can also be supported, including other 802.x communication protocols (e.g., WiMax, Wi-Fi, 3G), code division multiple access (CDMA), global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), etc.

Example Mobile Device Architecture

FIG. 2is a block diagram200of an example implementation of the mobile device100ofFIG. 1. The mobile device100can include a memory interface202, one or more data processors, image processors and/or central processing units204, and a peripherals interface206. The memory interface202, the one or more processors204and/or the peripherals interface206can be separate components or can be integrated in one or more integrated circuits. The various components in the mobile device100can be coupled by one or more communication buses or signal lines.

Sensors, devices, and subsystems can be coupled to the peripherals interface206to facilitate multiple functionalities. For example, a motion sensor210, a light sensor212, and a proximity sensor214can be coupled to the peripherals interface206to facilitate the orientation, lighting, and proximity functions described with respect toFIG. 1. Other sensors216can also be connected to the peripherals interface206, such as a positioning system (e.g., GPS receiver), a temperature sensor, a biometric sensor, a gyroscope, or other sensing device, to facilitate related functionalities.

A camera subsystem220and an optical sensor222, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips.

Communication functions can be facilitated through one or more wireless communication subsystems224, which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem224can depend on the communication network(s) over which the mobile device100is intended to operate. For example, a mobile device100may include communication subsystems224designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, the wireless communication subsystems224may include hosting protocols such that the device100may be configured as a base station for other wireless devices.

An audio subsystem226can be coupled to a speaker228and a microphone230to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.

The I/O subsystem240can include a touch screen controller242and/or other input controller(s)244. The touch-screen controller242can be coupled to a touch screen246. The touch screen246and touch screen controller242can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen246.

The other input controller(s)244can be coupled to other input/control devices248, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker228and/or the microphone230.

In one implementation, a pressing of the button for a first duration may disengage a lock of the touch screen246; and a pressing of the button for a second duration that is longer than the first duration may turn power to the mobile device100on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen246can, for example, also be used to implement virtual or soft buttons and/or a keyboard.

In some implementations, the mobile device100can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, the mobile device100can include the functionality of an MP3 player, such as an iPod™. The mobile device100may, therefore, include a 36-pin connector that is compatible with the iPod. Other input/output and control devices can also be used.

The memory interface202can be coupled to memory250. The memory250can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory250can store an operating system252, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. The operating system252may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, the operating system252can be a kernel (e.g., UNIX kernel).

The memory250may also store communication instructions254to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory250may include graphical user interface instructions256to facilitate graphic user interface processing; sensor processing instructions258to facilitate sensor-related processing and functions; phone instructions260to facilitate phone-related processes and functions; electronic messaging instructions262to facilitate electronic-messaging related processes and functions; web browsing instructions264to facilitate web browsing-related processes and functions; media processing instructions266to facilitate media processing-related processes and functions; GPS/navigation instructions268to facilitate GPS and navigation-related processes and instructions; camera instructions270to facilitate camera-related processes and functions; GUI adjustment instructions273to facilitate adjustment of graphical user interfaces and user interface elements in response to sensor data; and/or other software instructions272to facilitate other processes and functions. The memory250may also store other software instructions (not shown), such as web video instructions to facilitate web video-related processes and functions; and/or web shopping instructions to facilitate web shopping-related processes and functions. In some implementations, the media processing instructions266are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. An activation record and International Mobile Equipment Identity (IMEI)274or similar hardware identifier can also be stored in memory250.

FIG. 3illustrates an example process300for modifying a graphical user interface. For convenience, the process300is described below in reference to a device (e.g., device100,200) that performs the process.

One or more sensors of the device detect motion (e.g., a pattern of motion associated with pre-determined motion characteristics) of the device (302). One or more sensors on the device100/200(e.g., accelerometer172, motion sensor210, proximity sensor214, other sensors216, a gyroscope) can detect changes in the orientation, acceleration, proximity, etc. of the device and the degrees of the changes in orientation, acceleration, proximity, etc. caused by motion of the device and/or a user carrying the device. These changes in orientation, acceleration, proximity, etc. can be interpreted by the device as motion of the device. If the changes exhibit regularity or predictability or match predetermined criteria, the changes can be interpreted by the device as a pattern of motion. For example, a user of the device100can be walking and holding the device for use at the same time. The device100can be oscillating (e.g., bouncing up and down) due to the user walking or running. The oscillation can be detected by the sensors of the device. As another example, a user of the device100can be a passenger in an automobile and holding the device for use while the automobile is moving. The device100can be bouncing up and down as a result, which can be detected by the sensors of the device.

The motion of the device and/or the user can affect the user's accuracy when attempting to interact with a graphical user interface that is displayed on the touch-sensitive display of the device. For example, returning to the above example of the user carrying and using the device while walking, the device can bounce up and down due to motion of the carrying hand and arm while the user is walking. The bouncing can cause the user to touch the touch-sensitive display at an unintended location and select a user interface element that the user did not intend to select.

To address the problem described above, the detected pattern of device motion is mapped to one or more adjustments to the graphical user interface (304), and the graphical user interface of the device is adjusted using the mapped adjustments (306). The pattern of motion detected by the sensors is mapped to one or more adjustments of the graphical user interface of the device, including user interface elements in the graphical user interface, based on one or more criteria related to the detected pattern of motion. The criteria can include the type of the detected motion and the magnitude of the motion. The mapped adjustments are applied to the graphical user interface. The adjustments can mitigate the loss in accuracy in the user's attempts to select user interface elements in the graphical user interface by touching the touch-sensitive display. In some implementations, the mapping and adjustments can be made by the sensor processing instructions258and the GUI adjustment instructions273, respectively.

In some implementations, the device100can include a user-settable option to toggle the feature of adjustments to the graphical user interface based on detected device motion. That is, if the feature is disabled, no adjustments are made to the graphical user interface based on detected motion. If the feature is enabled, adjustments can be made to the graphical user interface based on detected motion.

In some implementations, the adjustment includes resizing of user interface elements and their corresponding touch areas (e.g., the area on the touch-sensitive display where a touch on the display selects the user interface element) in the graphical user interface. For example, rows corresponding to entries in a list interface (e.g., a list of contacts in a contact list where a row corresponds to a contact in the list, a list of media items where a row corresponds to a media item in the list, etc.) can be enlarged by increasing the height of each of the entry rows. The touch area corresponding to each one of the enlarged rows is also enlarged as a result. The enlarging gives the user a larger target touch area for a row, lessening the likelihood of unintentional selections. An example of the enlarging of rows corresponding to entries in a list is described below in reference toFIGS. 4A-4B.

As another example, the display objects104or106can be resized. One or more of the display objects104,106and their corresponding touch areas can be enlarged, increasing the target touch area for each of the resized display objects. An example of the enlarging of the display objects is described below in reference toFIGS. 5A-5B.

In some implementations, the adjustment includes a shift of the graphical user interface or of user interface elements in the graphical user interface. The graphical user interface/user interface elements can be shifted vertically and/or horizontally. In some implementations, the shift is in a direction opposite to the detected motion of the device; the shift attempts to relocate a user interface element to a position on the touch-sensitive display that the user is likely to touch if the user intended to select the user interface element in view of the motion of the device. An example of the shifting of user interface elements is described below in reference toFIG. 6.

In some implementations, the adjustment includes changing a sensitivity level of the touch-sensitive display. For example, the sensitivity level of the touch-sensitive display can be decreased. Decreasing the sensitivity level of the touch-sensitive display increases the pressure needed for a touch on the touch-sensitivity display to be recognized by the device. The increase in required pressure to select a user interface element can lead the user to be more deliberate in their attempts to touch the touch-sensitive display to select user interface elements.

In some implementations, the adjustment includes adjusting the target touch area of a user interface element based on an angle at which the device is being held. For example, if the device is held at an angle deviating from a default angle and which is more parallel than perpendicular with the ground, the target touch area of a user interface element can be enlarged. Optionally, the target touch area can also be skewed to account for the angle.

In some implementations, the adjustment includes enlarging some target touch areas and/or user interface elements relative to others. For example, a fisheye effect can be imposed on the target touch areas and the user interface to enlarge the elements and target areas nearer to the center of the “fisheye” relative to elements and target areas nearer to the periphery. The center of the “fisheye” need not be the center of the display; the center of the “fisheye” can be positioned over user interface elements in the user interface that are selected more often or are considered more important.

While several types of adjustments are described above, it should be appreciated that the adjustment to the graphical user interface made by the device can include any combination of the described types of adjustments and other suitable types of adjustments.

In some implementations, the amount of an adjustment is a predefined amount or percentage. For example, a user interface element can be resized by a predetermined amount of pixels or a predetermined percentage of the original size of the user interface element. In some other implementations, the amount of an adjustment is based on the amount of detected motion, amount of detected acceleration, amount of change in orientation from a starting position, or the like. For example, if the amount of acceleration from rest is small, the amount of the resizing or shifting of a user interface element is small as well. In some implementations, the amount of adjustment can be based on user preferences. For example, the user can configure (in a device options and settings interface, for example) a maximum allowable amount (e.g., a percentage) for a type of adjustment.

In some implementations, the adjustment includes interrupting actions initiated by the user with additional confirmation steps. Rather than shifting or resizing user interface elements by some amount, for example, the device can add confirmation dialogs or question interfaces to the user interface flow for particular actions and optionally also shift or resize user interface elements by a smaller amount. As an example, if a user attempts to make a call on device100while walking and a bouncing motion of the device is detected, the device100can display a confirmation dialog box displaying the contact or phone number to be dialed and asking the user to confirm that the contact or number that is displayed is the one to be called. The confirmation dialog box can have relatively large target touch areas for “Yes” and “No” buttons for the user to select to confirm or decline the call.

In some implementations, the device “learns” particular characteristics of the motion of the device and the user's interactions with the device in light of the motion of the device. For example, the device can measure magnitudes of the motion of the device due to the user's motions. As another example, the device can detect the user's mistakes in the selection of user interface elements (e.g., the user unintentionally selects a display object104or106and then quickly exits from the application corresponding to the selected display object). From the user mistakes, the device can look for patterns in the user's mistakes (e.g., user is consistently touching one side of the display but intended to touch the other side, the user is missing their intended targets in a consistent manner, etc.). From this learned information, the device can predict where the user will touch the touch-sensitive display while the device in motion and make the adjustments to the graphical user interface based on the predictions.

In some implementations, the device detects a motion of the device and compares the detected motion to one or more predetermined signatures of motion. The device can store multiple signatures of motion (e.g., a signature of a bouncing motion while the user is walking, a signature of a change in orientation, etc.) and, for each signature, corresponding adjustments to the graphical user interface. If the detected motion matches one of the predetermined signatures, the device adjusts the graphical user interface using the adjustments corresponding to the matching signature. In some other implementations, the device compares the detected motion and compares the detected motion to the signatures. The device uses the comparison to determine which signature is closest to the detected motion and applies the graphical user interface adjustments corresponding to the signature determined to be closest to the detected motion.

FIGS. 4A and 4Billustrate an example contact list user interface on an example mobile device.FIG. 4Aillustrates device100with a contact list400displayed on the display102. The contact list application400includes one or more contacts402A, with a row in the contact list400for each contact402A. A row402A can have a height H406. A user can touch the display102on the area of a contact402A to display the contact information for that contact. For example, if the user wishes to view the contact information for “John Adams,” the user touches the display over the area of the row for the contact “John Adams.” A toolbar404with buttons for various features related to phone functionality can also be displayed. Example features related to phone functionality can include a list of favorite contacts, a contact list, a log of recent calls, a keypad, and voicemail.

While the device is moving, the motion of the device can be detected. The device can change the size of the rows of the contacts in the contact list application400to give the user a larger target area for each contact. For example, the height of a row can be increased. As shown inFIG. 4B, the contact list application400has contacts402B which are located in rows whose heights have been increased to 2×H408. This gives the user a larger touch area with which to select a contact. In some implementations, the height of the toolbar404can be increased as well.

FIGS. 5A and 5Billustrate an example user interface of a device. InFIG. 5A, the device101is displaying display objects104A (objects124A,125A,134A,126A) and106A (objects114A,123A,132A,150A,148A,138A,152A) at their original sizes on the touch-sensitive display102. A display object104A or106A can have, for example, a width W502. The objects104A and106A can be resized in response to motion of the device that is detected by one or more sensors on the device.FIG. 5Bshows the device101with the resized objects104B (objects124B,125B,134B,126B) and106B (objects114B,123B,132B,150B,148B,138B,152B). The resized objects104B,106B are larger (e.g., have a width of 1.25×W504) than the original size objects104A and106A and has larger target touch areas than the original size objects104A and106A. This gives the user a larger touch area with which to select a display object104B or106B.

FIG. 6illustrates device101with a graphical user interface that includes display objects106. InFIG. 6, the display objects106are shifted, compared to the display objects106inFIG. 1B, vertically downward by a distance D602toward the bottom of the graphical user interface. The shift moves the target touch areas of the display objects106to a different position. In some implementations, the new position is a predetermined distance from the original position. In some other implementations, the new position is determined by the device based on a prediction of where the user will touch the touch-sensitive display if the user wanted to select the user interface element while the device is in motion.

Thus, particular embodiments have been described. Other embodiments are within the scope of the following claims.