The present disclosure relates to mobile devices, more particularly to user interfaces for mobile devices.
Mobile devices, such as cellular phones, laptop computers, pagers, personal digital assistants (PDA), and the like, have become increasingly prevalent. These devices provide the convenience of handheld computing with increased functionality. For example, an expanding variety of features and applications have become available that, in addition to conventional voice and data communications, permit users to connect to a variety of information and media resources, such as the Internet, as well as enable users to send and receive short messages, engage in multimedia playback, exchange electronic mail, perform audio-video capturing, participate in interactive gaming, manipulate data, and engage in other like functions and applications. Still further, these functions and applications may, at times, be concurrently accessed or even toggled between.
Unfortunately, as the richness and complexity of these functions and applications increase, the complexity of the user interface has increased commensurately. For example, mobile devices are being developed with complete alphabet keypads, such as QWERTY keypads including at least twenty-six keys, to facilitate more involved applications that typically demand “faster” user inputs, such as instant messaging applications. At the same time, manufacturers are also creating smaller devices with decreasing surface area on which to locate convenient user interfaces. As such, it has become an ever-growing challenge for users to suitably and efficiently interact with these user interfaces. From an ergonomics standpoint alone, traditional keypads are becoming less and less capable to meet the demands of user interactivity, while at the same time enabling smaller and smaller mobile device form factors. Accordingly, convenient, easy to manipulate user interfaces that are at the same time compact, continue to be objectives for improvement.
Therefore, a need exists for improved mobile device user interfaces. There exists a particular need for mobile devices with improved keypad user interfaces.
The above described needs are fulfilled, at least in part, by detecting a keystroke combination between at least a modification key and a particular key of a keypad, and determining an associated input based on the step of detecting. The modification key is included on a first face of a mobile device and the keypad is included on a second face of the mobile device. The first face and the second face substantially face opposite directions.
A mobile device is provided including a processor, a first face including a modification key, and a second face including a keypad. The first face substantially faces a first direction, and the second face substantially faces a second direction substantially opposite from the first direction. The processor is configured to detect a keystroke combination between at least the modification key and a particular key of the keypad for determining an associated input.
Still other aspects, features, and advantages are readily apparent from the following detailed description, wherein a number of particular embodiments and implementations, including the best mode contemplated, are shown and described. The disclosure is capable of other and different embodiments, and its several details are capable of modifications in various obvious respects, all without departing from the spirit and scope of the disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
Various exemplary embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements and in which:
An apparatus, method, and software for providing a user interface on a mobile device are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of exemplary embodiments. It is apparent, however, to one skilled in the art that exemplary embodiments may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring exemplary embodiments.
Although exemplary embodiments are described with respect to mobile devices and, in particular, to mobile communication devices, it is recognized that various exemplary embodiments have applicability to other devices and technologies. Furthermore, while specific reference is made to QWERTY-style keypad interfaces, it is contemplated that various exemplary embodiments are applicable to other keypad interface arrangements.
Keys 101-119 of key set 100 may be arranged in any suitable manner, such as positioned in one or more arrays, matrices, or other suitable patterns. According to one embodiment, keys 101-119 are positioned in two, five key columns that are arranged about an imaginary reference line 121 extending in an imaginary “Y” direction. That is, keys 101-109 may be arranged in column 123, while keys 111-119 may be arranged in column 125. As shown, columns 123 and 125 are arcuately formed and respectively curve away from reference line 121 in substantially opposite directions, such as in opposite directions substantially extending in an imaginary “X” direction. In this manner, keys 103 and 113 may serve as respective apexes of the curves of columns 123 and 125, such that keys 103 and 113 may be dimensionally closest to reference line 121, while keys 109 and 119 may be dimensionally furthest from reference line 121. It is noted, however, that any one or more of keys 101-119 of columns 123 and 125 may serve as respective apexes of columns 123 and 125. According to particular implementations, the curves of columns 123 and 125 are configured to correspond to the outward curves formed by the tips of the fingers of an average user's left and right hands. In this manner, keys 101-119 may be positioned having a first dimensional pitch 127 extending in the imaginary “Y” direction, and a second dimensional pitch 129 extending in the imaginary “X” direction. Pitches 127 and 129 may be equal to or not equal to one another, and may be held constant or varied between respective keys 101-119 of key set 100, such as in the respective “Y” and/or “X” directions. While shown in the described manner, it is contemplated that columns 123 and/or 125 may be otherwise formed, such as formed in one or more linear arrangements, variable arrangements, or other geometric formations or other suitable patterns. Moreover, while columns 123 and 125 are shown symmetrically arranged about imaginary reference line 121, asymmetrical formations are also contemplated.
As previously mentioned, keys 101-119 of key set 100 may be associated with one or more inputs, such as one or more textual characters, symbolic characters, etc. In exemplary embodiments, character input associations for keys 101-119 may conform to a Roman script QWERTY-like key set arrangement; however, other suitable key set styles are contemplated, such as an AZERTY-style, DVORAK-style, QWERTZ-style, etc., as well as other suitable scripts, such as Arabic, Greek, Hebrew, Japanese, Latin, Russian, etc. Before describing the illustrated character input association for keys 101-119, the character input associations for a conventional QWERTY key set will be described.
As seen in
As is well known, key set 200 can be utilized in a two-hand touch typing fashion, i.e., a typing method wherein a user utilizes their fingers and thumbs of their two-hands to strike (or otherwise actuate) the keys of key set 200 without having to use their sense of sight to find the keys. According to one common approach, two-hand touch typing typically entails a user placing their eight fingers of their left and right hands in a horizontal row along the middle (or “home”) row of keys of key set 200. More specially, fingers 201, 203, 205, and 207 of left hand 209 are respectively placed on the “F,” “D,” “S,” and “A” keys, while fingers 211, 213, 215, and 217 of right hand 219 are respectively placed on the “J,” “K,” “L,” and “Semi-Colon (;)” keys. As such, the “F,” “D,” “S,” and “A” keys can be considered “home” keys for fingers 201-207 of hand 209, while the “J,” “K,” “L,” and “Semi-Colon (;)” keys can be considered “home” keys for fingers 211-217 of hand 219. A user may easily strike these “home” keys without having to move their fingers about key set 200. The corollary is that to strike one of the remaining keys of key set 200, the user must first move one of their fingers to a desired key and then must correspondingly strike the desired key.
Consequently, the fingers of hands 209 and 219 may be utilized to strike (or otherwise actuate) certain groups of keys. For instance, finger 201 may be globally utilized to strike keys “R,” “F,” and “V” of key column 221, as well as keys “T,” “G,” and “B” of key column 223. Meanwhile, finger 211 may be globally utilized to strike keys “U,” “J,” and “M” of key column 225, as well as keys “Y,” “H,” and “N” of key column 227. Finger 203 may be globally utilized to strike keys “E,” “D,” and “C” of key column 229, while finger 213 may be globally utilized to strike keys “I,” “K,” and “Comma (,)” of key column 231. Still further, finger 205 may be globally utilized to strike keys “W,” “S,” and “X” of key column 233, while finger 215 may be globally utilized to strike keys “O,” “L,” and “Period (.)” of key column 235. As such, fingers 207 and 209 may be globally utilized to respectively strike keys “Q,” “A,” and “Z” of key column 237 and keys “P,” “Semi-Colon (;)” and “Slash (/)” of key column 239. While not illustrated, thumbs 241 and 243 are typically utilized to strike a spacebar. Utilizing key set 200 in conjunction with the aforementioned two-hand touch typing finger associations can enable users to efficiently input characters to a host device.
With this understanding of key set 200, the character input associations for keys 101-119 of key set 100 will now be described. According to exemplary embodiments, keys 101-119 have character input associations corresponding to one or more of the character input associations of key set 200. That is, fewer keys (e.g., ten keys) may be provided for via key set 100 than key set 200 for a same amount of associated character inputs, e.g., thirty character inputs. In this manner, however, the character input associations provided for via keys 101-119 may still preserve the relationship between keys and key columns described in connection with
When key set 100 is implemented on a host device (such as illustrated in
Accordingly, when key set 100 is implemented on a host device, such as the mobile device of
According to exemplary embodiments, the previously mentioned modification key(s) may be utilized to dynamically switch between “default” input characters associated with keys 101-119 of key set 100, and the “other” input characters associated with keys 101-119. In one particular implementation, key set 100 may include two modification keys that when actuated, for example, in combination with a particular key of key set 100 may dynamically modify an input associated with the particular key. For instance, if a first modification key is actuated in combination with a particular key of key set 100, then a first input character associated with the particular key may be input to the host device. This first input character may be considered a first modified input. In this way, if a second modification key is actuated in combination with the particular key of key set 100, then a second input character associated with the particular key may be input to the host device. This second input character may be considered a second modified input. If only the particular key is actuated, then a third input character associated with the particular key may be input to the host device. This third input character may be considered a default input character. Table 3 provides an exemplary mapping relationship between input characters associated with keys 101-119 of key set 100 and default and modified input cases.
As such, key set 100 can provide a more efficient and more compact user interface. For instance, a user need not move their fingers about key set 100 as much because a plurality of inputs may be associated with each individual key of key set 100. Moreover, these pluralities of input associations also enable key set 100 to provide a user interface that includes a less number of keys. Furthermore, when implemented on a host device, the aforementioned modification keys may be positioned so that a user can actuate them utilizing their thumbs, while keys 101-119 may be positioned so that the user can actuate keys 101-119 utilizing their fingers. When engaging in two-hand touch typing, a user's fingers are not required to move any more than necessary due, in part, to the fact that the user's thumbs, which are normally only utilized to actuate a spacebar, can be efficiently employed to ensure a desired input is dynamically associated with the particular key that is (or will be) actuated.
More specifically, the housing includes a first major face (e.g., a front side) 323 and a second major face (e.g., a back side) 325 bounded by one or more minor faces 327, 329, 331, and 333. Minor faces 327 and 329 may respectively relate to left and right sides of mobile device 300, while minor faces 331 and 333 may respectively relate to top and bottom sides of mobile device 300. It is noted that these directional references are merely exemplary as they are dependent upon a particular orientation and particular vantage point of mobile device 300. In certain embodiments, minor faces 327 and 329 can be contoured in such a manner as to provide an ergonomic “look and feel” for mobile device 300, such as to provide a comfortable “fit” when held by a user in one or more of their hands. This ergonomic “look and feel” may additionally promote user interactivity with and input efficiency to mobile device 300, as the “look and feel” may enable a user's fingers to be more naturally and comfortably placed upon one or more of the keys of keypad 305. The housing of mobile device 300 may also include one or more other ergonomic features, such as one or more finger rests (e.g., finger rests 315, 317, 319, 321, 323, 325, 327, 329) and/or one or more thumb rests (e.g., thumb rests 331 and 333). Rests 315-333 may also enable a user's fingers to be more naturally and comfortably placed upon one or more of the keys of keypad 305. Furthermore, rests 315-333 may provide more surface area upon which a user's fingers and thumbs may bias against when the user actuates the various keys of keypads 303 and 305, as well as modification keys 309-315 and user controls 321. While the housing is shown in a brick-like (or candy bar-like) fashion, any other suitable housing designs may be utilized, such as a fold (or clamshell) housing, slide housing, swivel housing, and/or the like.
As seen in
In exemplary embodiments, major face 323 includes modification keys 309-315 for dynamically modifying an input (e.g., character input) associated with a particular key of keypad 305, which may be provided for via major face 325. For instance, modification keys 309-315 may be utilized (e.g., actuated in concert with a particular key of keypad 305) to toggle between a plurality of character inputs that may be associated with a particular key of keypad 305. In one particular implementation, modification keys 309 and 311 may be utilized to dynamically modify character inputs associated with the keys of keypad 305 according to the “first modified inputs” of Table 3. Meanwhile, modification keys 313 and 315 may be utilized to dynamically modify character inputs associated with the keys of keypad 305 according to the “second modified inputs” of Table 3. As such, the keys of keypad 305 may have “default” character inputs according to the “default inputs” of Table 3.
In one implementation, the positioning of modification keys 309-315 about major face 323 may relate to the manner in which modification keys 309-315 modify associated character inputs associated with the keys of keypad 305. More specifically, modification keys 309-315 may be positioned about major face 323 in such a manner that, when mobile device 300 is oriented and viewed as illustrated in
To facilitate two-hand touch typing, modification keys 309-315 may be included on a first face (e.g., major face 323) of mobile device 300, while the keys of keypad 305 may be provided on a second face (e.g., major face 325) of mobile device 300. As major faces 323 and 325 substantially face in opposite directions, modification keys 309-315 and the keys of keypad 305 may substantially face in opposite directions. When mobile device 300 is held in a user's hands with display 301 substantially facing the user, modification keys 309-315 may be actuated via the user's thumbs, while the keys of keypad 305 may be actuated via the user's fingers. In this manner, the keys of keypad 305 and modification keys 309-315 can be utilized by a user to engage in two-hand touch typing, which may be further facilitated by one or more tactile identifiers (e.g., tactile identifiers 357 and 359). Tactile identifiers 357 and 359 may be utilized to locate certain keys of keypad 305. For instance, the aforementioned “home” keys of key set 100 may be more easily identified by a user through the user's sensory touch detection of tactile identifiers 357 and 359.
Contrastingly, keypad 303 may be a conventional keypad typically provided on telephony capable devices. Namely, keypad 303 may present numeric characters along with Roman script characters on a single interface, which may be configured for one-hand or two-hand thumb-typing. For example, keypad 303 may conform to one or more of the International Telecommunications Union (ITU) standards for the presentation of alphanumeric keys on devices having telephony capabilities. In the illustrated embodiment, keypad 303 is provided in accordance with ITU Standard E.161, entitled “Arrangement of Digits, Letters, and Symbols on Telephones and Other Devices that can be used for Gaining Access to a Telephone Network,” which is incorporated herein, by reference, in its entirety. This standard promulgates a ten or twelve key interface for presenting numeric characters “0” through “9” on a single keypad along with Roman script characters “A” through “Z.” In certain instances, other glyphs may be provided for, such as an asterisk (*), comma (,), number sign (#), period (.), semi-colon (;), slash (/), etc. As such, any individual key may be associated with one or more potential inputs, such that inputting a particular character may require certain keys to be actuated multiple times until a desired input is ultimately achieved. Actuation is typically performed via a user's thumbs. While useful in some instances, these keypad interfaces are becoming more and more unsuitable for applications demanding “faster” inputs, such as instant messaging, word processing, and other like text-based applications. Since keypad 305 and modification keys 309-315 can enable two-hand touch typing, keypad 305 and modification keys 309-315 can enhance user interactivity and increase user input efficiency to mobile device 300. It is contemplated that modification keys 309-315 may also be utilized to dynamically modify inputs (e.g., character inputs) associated with keys of keypad 303. In this manner, modification keys 309-315 may increase user interactivity and increase user input efficiency of keypad 303, as well. It is also noted that keypad 305 may be utilized in a similar manner as keypad 303, i.e., wherein individual keys may be associated with one or more potential inputs, such that inputting a particular character may require certain keys to be actuated multiple times until a desired character input is achieved.
Accordingly, when keypad 305 is provided on major face 325 (e.g., a typically under, if ever, utilized face), the available surface area of mobile device 300 may be more efficiently utilized. This may enable certain conventional components (e.g., display 301, keypad 303, etc.) to occupy more surface area of mobile device 300 than would otherwise be available. In other instances, the keys of keypad 305 may occupy more surface area than conventionally available to, for instance, conventional keypads, such as keypad 303. This can enable key dimensions and dimensional pitches between keys that are suitable for a convenient, easy to manipulate keypad interface. Also, mobile device 300 may be provided having a smaller overall form factor, as the available surface area of mobile device 300 may be more efficiently utilized.
User interface 601 includes one or more of the following: display 301, keys 607, microphone 307, and/or transducer (or speaker) 319. Display 301 provides a graphical interface that permits a user of mobile device 300 to view, for instance, call status, configurable features, contact information, dialed digits, directory addresses, menu options, operating states, time, and other information, such as character inputs to mobile device 300 via keys 607. The graphical interface may include icons and menus, as well as other text, soft controls, symbols, and/or widgets. In this manner, display 301 enables users to perceive and interact with the various features of mobile device 300.
Keys 607 may be included as one or more keypad interfaces. For instance, keys 607 may be provided as keypads 303 and 305, as well as modification keys 309-315. Thus, keys 607 may provide for a variety of user input operations. For example, keys 607 may include alphanumeric keys for permitting entry of alphanumeric information, such as configuration parameters, contact information, directory addresses, electronic mail messages, notes, phone lists, short text messages, word processing inputs, etc. In addition, keys 607 may represent other input controls, such as user controls 321, e.g., one or more button controls, dials, joysticks, and the like. Particular keys of a plurality of keys 607 may be utilized for different functions of mobile device 300, such as for conducting voice communications, short messaging, multimedia messaging, playing interactive games, etc. Keys 607 may include a “send” key for initiating or answering received communication sessions, and an “end” key for ending or terminating communication sessions. Special function keys may also include menu navigation keys, for example, for navigating through one or more menus presented via display 301, to select different mobile device functions, profiles, settings, etc. Other keys (e.g., modification keys 309-315) may be provided for dynamically modifying inputs (e.g., character inputs) associated with particular other keys, e.g., keys associated with keypads 303 and/or 305. Still further, certain key associated with mobile device 300 may include a volume key, an audio mute key, an on/off power key, a web browser launch key, etc. Keys or key-like functionality may also be embodied through one or more touch screens and associated soft controls presented via display(s) 301.
In this manner, actuation of keys 607 may be detected and/or identified by keypad control module 603 and/or detectors 607. For instance, keypad control module 603 may generate signals or commands for updating a presentation of display 301 or modifying a function of mobile device 300 in response to one or more signals provided by detectors 609 detecting actuation of one or more of keys 607. In particular, detectors 609 may be functionally interposed between keys 607 and controller (or processor) 611. Thus, keypad control module 603 and/or detectors 609 may convert “physical” actuation of one or more keys 607 into individual characters or other types of input for processing by controller 611. In cases of noncontact key technologies, keypad control module 603 and/or detectors 609, in the form of, for instance, firmware (possibly programmed into an application specific integrated circuit), may provide functional conversion between sensing “virtual” actuation of one or more of keys 607 and appropriate corresponding inputs. In this manner, keypad control module 603 may access one or more input mapping tables for generating associated inputs when one or more of keys 607 are actuated. These mapping tables may relate to the exemplary mapping relationships provided in Table 3. Inputs generated by keypad control module 603 may be communicated to controller 611 for executing applications requiring and/or expecting the entering of information via keys 607.
Microphone 307 converts spoken utterances of a user into electronic audio signals, while speaker 319 converts audio signals into audible sounds. Microphone 307 and speaker 319 may operate as parts of a voice (or speech) recognition system. Thus, a user, via user interface 605, can construct user profiles, enter commands, generate user-defined policies, initialize applications, input information (e.g., textual information), manipulate screen indicia (e.g., cursors), select options from various menu systems, and perform other like tasks and/or functions.
Communications circuitry 601 enables mobile device 300 to initiate, receive, process, and terminate various forms of communications, such as voice communications (e.g., phone calls), electronic mail messages, short message service (SMS) messages (e.g., text and picture messages), and multimedia message service (MMS) messages, etc. In other instances, communications circuitry 601 enables mobile device 300 to transmit, receive, and process voice signals and data, such as voice communications, endtones, image files, video files, audio files, ringbacks, ringtones, streaming audio, streaming video, video game information, etc. Communications circuitry 601 includes audio processing circuitry 613, controller (or processor) 611, memory 615, transceiver 617 coupled to antenna 619, and wireless controller 621 (e.g., a short range transceiver) coupled to antenna 623.
A specific design and implementation of communications circuitry 601 can be dependent upon one or more communication networks for which mobile device 300 is intended to operate. For example, mobile device 300 may be configured for operation within any suitable wireless network utilizing, for instance, an electromagnetic (e.g., radio frequency, optical, and infrared) and/or acoustic transfer medium. In various embodiments, mobile device 300 (i.e., communications circuitry 601) may be configured for operation within any of a variety of data and/or voice networks, such as advanced mobile phone service (AMPS) networks, code division multiple access (CDMA) networks, general packet radio service (GPRS) networks, global system for mobile communications (GSM) networks, internet protocol multimedia subsystem (IMT) networks, personal communications service (PCS) networks, time division multiple access (TDMA) networks, universal mobile telecommunications system (UTMS) networks, or a combination thereof. Other types of data and voice networks (both separate and integrated) are also contemplated, such as microwave access (MiMAX) networks, wireless fidelity (WiFi) networks, satellite networks, and the like.
Wireless controller 621 acts as a local wireless interface, such as an infrared transceiver and/or a radio frequency adaptor (e.g., Bluetooth adapter), for establishing communication with an accessory, hands-free adapter, another mobile communication device, computer, or other suitable device or network.
Processing communication sessions may include storing and retrieving data from memory 615, executing applications to allow user interaction with data, displaying video and/or image content associated with data, broadcasting audio sounds associated with data, and the like. Accordingly, memory 615 may represent a hierarchy of memory, which may include both random access memory (RAM) and read-only memory (ROM). Computer program instructions, such as application instructions for detecting and identifying inputs associated with actuated keys of keys 607, can be stored in non-volatile memory, such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; however, may be stored in other types or forms of storage. Memory 615 may be implemented as one or more discrete devices, stacked devices, or integrated with controller (or processor) 611. Memory 615 may store program information, such as one or more user profiles, one or more user defined policies, one or more user interface control parameters, one or more mapping tables, etc. In addition, system software, specific device applications, program instructions, program information, or parts thereof, may be temporarily loaded to memory 615, such as to a volatile storage device, e.g., RAM. Communication signals received by mobile device 300 may also be stored to memory 615, such as to a volatile storage device.
Controller 611 controls operation of mobile device 300 according to programs and/or data stored to memory 615, as well as based on user input received through one or more of the components of user interface 605. Control functions may be implemented in a single controller (or processor) or via multiple controllers (or processors). Suitable controllers may include, for example, both general purpose and special purpose controllers, as well as digital signal processors, local oscillators, microprocessors, and the like. Controller 611 may also be implemented as a field programmable gate array (FPGA) controller, reduced instruction set computer (RISC) processor, etc. Controller 611 may interface with audio processing circuitry 613, which provides basic analog output signals to speaker 319 and receives analog audio inputs from microphone 307.
Controller 611, in addition to orchestrating various operating system functions, also enables execution of software applications, such as instant messaging applications, word processing application, etc., stored to memory 615. According to particular implementations, memory 615 may be utilized to store one or more interactive games configured to acquaint users with keypad 305 and modification keys 309-315. The interactive game may relate to a space invaders game incorporating text, Tetris with letters, and the like. One exemplary interactive game is explained in more detail in accordance with
While exemplary embodiments of mobile device 300 have been described with respect to a two-way radio frequency communication device having voice and data communication capabilities, embodiments of mobile device 300 are not so limited. For instance, mobile device 300 may additionally (or alternatively) correspond to any suitable wireless two-way communicator. For example, mobile device 300 can be a cellular phone, two-way trunked radio, combination cellular phone and personal digital assistant (PDA), smart phone, cordless phone, satellite phone, or any other suitable mobile communication device with voice and/or data communication capabilities, such as a mobile computing device.
At step 701, keypad control module 603 initializes the keys of keypad 305 and modification keys 309-315. For example, keypad control module 603 may implement instructions stored to memory 615 in response to a user powering on mobile device 300. Powering on mobile device 300 may also cause controller 611 to provide, for instance, a graphical interface to a user via display 301. The graphical interface may include one or more input fields, menus, options, selections, etc., that enable users to input or otherwise interact with a function or application of mobile device 300. These fields, menus, options, selections, etc., can be populated, manipulated, or otherwise interacted with via user actuation one or more of the keys of keypad 305 (e.g., key 361) and/or modification keys 309-315 (e.g., modification key 309 or 313).
Accordingly, per step 703, mobile device 300 (e.g., keypad control module 603) monitors the keys of keypad 305 and modification keys 309-315 for user interaction. In certain embodiments, user actuation of the keys of keypad 305 and/or modification keys 309-315 may be monitored and, thereby, detected via one or more detectors 609, e.g., one or more mechanically actuated electrical conductors, motion sensors, optical sensors, pressure sensors, etc. As such, in step 705, keypad control module 603 determines whether one or more keystrokes to keypad 305 and/or modification keys 309-315 have been detected. Keypad control module 603 may determine whether a keystroke (or keystroke combination) has occurred, if one or more signals are provided to keypad control module 603 via detectors 609 relating to actuation of keypad 305 and/or modification keys 309-315. If no keystrokes are detected, then keypad control module 603 continues to monitor the keys of keypad 305 and modification keys 309-315.
If one or more keystrokes are detected, then keypad control module 603 determines, per step 707, whether a keystroke combination has been detected by, for example, detectors 609. If a keystroke combination is not detected, e.g., only key 361 is actuated, then keypad control module 603 may determine (at step 709) a default input associated with the actuated key. According to particular embodiments, this determination may be facilitated by reference to one or more mappings stored to, for instance, memory 615. As previously mentioned, these mappings provide tables correlating keystrokes and keystroke combinations to associated input characters. For example, keypad control module 603 may determine, based on these tables, that a default input associated with actuation of key 361 is character input “D.” If, however, a keystroke combination is detected, e.g., key 361 is actuated in concert with modification key 309 or 313, then keypad control module 603 may determine (per step 711) a modified input associated with the actuated keys. For instance, keypad control module 603 may determine, based on the mapping tables, that a modified input associated with actuation of key 361 in concert with modification key 309 may correspond to character input “E.” As another example, keypad control module 603 may determine, based on the mapping tables, that a modified input associated with actuation of key 361 in concert with modification key 313 may correspond to character input “C.” According to certain embodiments, if a modification key (e.g., modification key 309) is actuated before a key of keypad 305, keypad control module 603 may wait for a predetermined time period for a key of keypad 305 to be actuated before determining an associated character input. In this manner, modification keys 309-315 need not necessarily be actuated in direct concert with a particular key of keypad 305 for a user to input a keystroke combination. As such, a determined character input may be provided to controller 611 so that controller 611 may, per step 713, update a presentation of display 301, such as, for example, updating display 301 to present one of characters “E,” “D,” or “C” corresponding to the detected keystroke or keystroke combination.
Referring to
As the user grows more accustomed to and comfortable with keypad 305, visual indicators 801 and 803 may be provided as shown in
According to exemplary embodiments, as a user becomes acquainted with keypad 305 and modification keys 309-315, the character sequences of the interactive game may require greater skill and finger dexterity from users. For instance, as seen in
While the disclosure has been described in connection with a number of embodiments and implementations, the disclosure is not so limited, but covers various obvious modifications and equivalent arrangements, which fall within the purview of the appended claims. Although features of the disclosure are expressed in certain combinations among the claims, it is contemplated that these features can be arranged in any combination and order.