While many Chrome OS devices have touch screens, for games the best interaction experience on these large-screen devices is often delivered through mouse, keyboard, and gamepad. The mobile gaming world is often touch-centric and some thought needs to be given into how to provide the best experience for users not using touch.
Begin by checking out the best practices for adding keyboard, mouse, and game controllers support. You will want to pay special attention to the case where users have keys held down or may be pressing multiple keys.
Touch-based actions are okay for Chromebooks with touchscreens, but it’s important to also include thoughtful physical controls for a great experience. For example, mouse input is great for adjusting the view or aiming, but should not be required for performing actions - if a mobile game has an on-screen menu that allows a user to use a torch, a sword, or a shield by pressing a button with their thumb, requiring them to click these buttons with a mouse will provide a poor experience. Instead, keyboard keys should be designated to trigger each action by overriding
onKeyDown. See the input compatibility page for details and code.
First person viewpoint games look best on the desktop when they implement mouse capture. This hides the mouse pointer and allows the user to move the viewpoint, to aim, to steer, etc., by using the mouse. Below is a basic mouse capture demo that records the pointer position and button states after the user clicks a text view named
text_clickme. See the Android pointer capture documentationfor more information.
Chat features can be an important component of multiplayer games. Take some time to think about how users will interact with your game’s chat feature while playing. In particular, if they are playing with the keyboard, they should not have to use the mouse or touchscreen to access chat or send messages.
One pattern could be to have a keyboard key focus the chat box, and handle the enter key to send messages.
Check out the keyboard documentation on the Android input compatibility page.
Drawing apps and swipe-based games can take advantage of stylus input on Chrome OS devices. See the stylus input page for more details.
Chromebooks support up to four game controllers. Developers should use the standard Android Game Controller APIsto support them.
Buttons are mapped to common values following a common mapping. Unfortunately, not all game controller manufacturers follow the same mapping conventions. Allowing your users to select from different popular controller mappings can provide a much better experience.
How to support all of the different input types that are available to chromebooks.
How to take your current web site and enhance it to make it installable, work great with touch and stylus, and make it even more capable.
After optimizing for large screens, active Infinite Painter installations and overall in-app activity have both grown substantially.