Input compatibility

Navigation

Keyboard navigation is rarely implemented in touch-centric apps, but users expect it when they are using an app and have their hands on a keyboard. It can also be essential for users with accessibility needs on both phones and desktop devices.

For many apps, simple arrow key and tab navigation is all that is needed and is mostly handled automatically by the Android framework. For example, a view of a Button is focusable by default, and keyboard navigation should generally work without any additional code. In order to enable keyboard navigation for views that are not focusable by default, developers should mark them as focusable. This can be done programmatically or in XML, as shown below. See the Focus Handling⁠ documentation for more information.

yourView.isFocusable = true

Alternatively you can set the focusable attribute in your layout file:

android:focusable="true"

Once focus is enabled, the Android framework will create a navigational mapping for all focusable views based on their position. This usually works as expected and no further work is needed. When the default mapping is not correct for an app’s needs, it can be overridden as follows:

// Arrow keys
yourView.nextFocusLeftId = R.id.view_to_left
yourView.nextFocusRightId = R.id.view_to_right
yourView.nextFocusTopId = R.id.view_above
yourView.nextFocusBottomId = R.id.view_below

// Tab key
yourView.nextFocusForwardId = R.id.next_view

It is good practice to try to access every piece of your app’s functionality before each release using the keyboard only. It should be easy to access the most common actions without mouse of touch input.

Keystrokes

For text input that would be handled by an on-screen virtual keyboard (IME⁠) such as an EditText, apps should behave as expected on ChromeOS with no additional work from the developer. For keystrokes that cannot be anticipated by the framework, apps will need to handle the behavior themselves. This is especially true for apps with custom views.

Some examples are chat apps that use the enter key to send a message, media apps that start/stop playback with the space key, and games that control movement with the w,a,s, and d keys.

Most apps override the onKeyUp⁠ event and add the expected behavior for each received keycode, as shown below.

override fun onKeyUp(keyCode: Int, event: KeyEvent): Boolean {
    return when (keyCode) {
        KeyEvent.KEYCODE_ENTER -> {
            sendChatMessage()
            true
        }
        KeyEvent.KEYCODE_SPACE -> {
            playOrPauseMedia()
            true
        }
        else -> super.onKeyUp(keyCode, event)
    }
}

Using onKeyUp prevents apps from receiving multiple events if a key is held down or released slowly. Games and apps that expect users to hold down keyboard keys can look for the onKeyDown⁠ event.

Depending on an app’s needs, overriding onKeyUp for the entire Activity usually provides the needed behavior. If desired, an onKeyListener⁠ can be added to a specific view instead. For example an app may only listen for the Enter key in specific EditText, and not the Activity, in order to implement send functionality only when the user is typing in a chat box.

When you add keyboard support, follow the Android Keyboard handling documentation⁠.

Shortcuts

Common Ctrl, Alt, and Shift-based shortcuts are expected in desktop environments. If an app does not implement them, the experience can feel frustrating and broken to users. Advanced users also appreciate shortcuts for frequently used app-specific tasks. Shortcuts make an app easier to use and differentiate it from apps that don’t have shortcuts.

Some common shortcuts include save (Ctrl+S), undo (Ctrl+Z), and redo (Ctrl+Shift+Z). For an example of some more advanced shortcuts, see the list of VLC Media Player shortcut keys⁠.

Shortcuts can be implemented using dispatchKeyShortcutEvent⁠. This intercepts all meta-key combinations (Alt, Ctrl, and Shift) for a given keycode. To check for a specific meta-key, use KeyEvent.isCtrlPressed()⁠, KeyEvent.isShiftPressed()⁠, KeyEvent.isAltPressed()⁠, or KeyEvent.hasModifiers()⁠.

Separating shortcut code from other keystroke handling (such as onKeyUp or onKeyDown) can make code maintenance easier and maintains the default acceptance of meta-keys without having to manually implement meta-key checks in every case. Allowing all meta-key combinations can also be more convenient for users who are accustomed to different keyboard layouts and operating systems.

override fun dispatchKeyShortcutEvent(event: KeyEvent): Boolean {
  return when (event.keyCode) {
    KeyEvent.KEYCODE_O -> {
      openFile() // Ctrl+O, Shift+O, Alt+O
      true
    }
    KeyEvent.KEYCODE_Z-> {
      if (event.isCtrlPressed) {
        if (event.isShiftPressed) {
          redoLastAction() // Ctrl+Shift+Z pressed
          true
        } else {
          undoLastAction() // Ctrl+Z pressed
          true
        }
      }
    }
    else -> {
      return super.dispatchKeyShortcutEvent(event)
    }
  }
}

You can also implement shortcuts in onKeyUp by checking for KeyEvent.isCtrlPressed()⁠, KeyEvent.isShiftPressed()⁠, or KeyEvent.isAltPressed()⁠ in the same manner as above. This can be easier to maintain if the meta-behavior is more of a modification to an app behavior than a shortcut. For example, when W means “walk forward” and Shift+W means “run forward”.

override fun onKeyUp(keyCode: Int, event: KeyEvent): Boolean {
  return when(keyCode) {
    KeyEvent.KEYCODE_W-> {
      if (event.isShiftPressed) {
        if (event.isCtrlPressed) {
          flyForward() // Ctrl+Shift+W pressed
          true
        } else {
          runForward() // Shift+W pressed
          true
        }
      } else {
        walkForward() // W pressed
      }
    }
    else -> super.onKeyUp(keyCode, event)
  }
}

Right-click

Any actions that cause an app to show a context menu, like a long-press on a list item, should also react to right-click events. To handle right-click events, apps should register a View.OnContextClickListener⁠. For details on constructing a context menu, see the Android context menu documentation⁠

yourView.setOnContextClickListener {
  showContextMenu()
  true
}

Hover

Developers can make their app layouts feel polished and easier to use by handling hover events. This is especially true for custom views. The two most common examples of this are:

• Indicating to users if an element has interactive behavior, such as being clickable or editable, by changing the mouse pointer icon
• Adding visual feedback to items in a large list or grid when the pointer is hovering over them

// Change the icon to a "hand" pointer on hover,
// Highlight the view by changing the background.
yourView.setOnHoverListener { view, _ ->
  addVisualHighlighting(true)
  view.pointerIcon =
    PointerIcon.getSystemIcon(applicationContext,
    PointerIcon.TYPE_HAND)
  false // listener did not consume the event.
}

Drag-and-Drop

In a multi-window environment, users expect to be able to drag-and-drop items between apps. This is true for ChromeOS devices as well as tablets, phones, and foldables in split-screen mode.

Developers should consider whether users are likely to drag items into their app. Some common examples include: photo editors should expect to receive photos, audio players should expect to receive audio files, and drawing programs should expect to receive photos.

To add drag-and-drop support, follow the Android Drag-and-Drop documentation⁠ and take a look at this ChromeOS blog post⁠.

Special considerations for ChromeOS

• To handle files from the ChromeOS Files app, look for the MIME type application/x-arc-uri-list
• Remember to request permission via requestDragAndDropPermissions to access items dragged in from outside the app
• An item must have the View.DRAG_FLAG_GLOBAL flag in order to be dragged out to other applications

Multi-select support

If your app contains lists or grids, consider whether your users would benefit from support for multi-select. A high-quality multi-select experience with mouse and trackpad often includes features such as band selection. Implementing this on your own can be challenging, but you can leverage the Recyclerview Selection library⁠.

Advanced pointer support

Apps that do advanced handling of mouse and touchpad input should follow the Android documentation for View.onGenericMotionEvent()⁠ and use MotionEvent.getSource()⁠ to distinguish between SOURCE_MOUSE⁠ and SOURCE_TOUCHSCREEN⁠.

Examine the MotionEvent to implement the required behavior:

• Movement generates ACTION_HOVER_MOVE events
• Buttons generate ACTION_BUTTON_PRESS and ACTION_BUTTON_RELEASE events. You can also check the current state of all mouse/trackpad buttons using getButtonState().
• Mouse wheel scrolling generates ACTION_SCROLL events

Historical points

Android batches input events and delivers them once per frame. A stylus pen can report events at much higher frequencies than the display. When creating drawing apps, it is important to check for events that may be in the recent past by using the getHistorical APIs:

• MotionEvent.getHistoricalX()
• MotionEvent.getHistoricalY()
• MotionEvent.getHistoricalPressure()
• MotionEvent.getHistoricalAxisValue()

Palm rejection

ChromeOS attempts to recognize when a user’s palm is resting on the touchscreen. However, this is not always possible. Sometimes a touch event might be reported to the app before the OS recognizes it as a palm. In that case, touches will be cancelled by reporting an ACTION_CANCEL event.

This event tells the app that certain touches are invalid and it should undo all interactions caused by those touches. For example, a drawing app might temporarily draw new lines as soon as they are received to provide the lowest latency, but only commit them permanently to the canvas once the touch series is finished cleanly. If touch events are cancelled in the meantime, the temporary lines can be easily erased.

Note-taking apps

ChromeOS has a special intent that surfaces registered note-taking apps to users. To register an app as a note-taking app, add the following to the Android manifest:

  <intent-filter>
    <action android:name="org.chromium.arc.intent.action.CREATE_NOTE" />
    <category android:name="android.intent.category.DEFAULT" />
  </intent-filter>

When an app is registered, the user can select it as the default note-taking app. When a new note is requested, the app should create an empty note ready for stylus input. When the user wishes to annotate an image (such as a screenshot or downloaded image), the app launches with ClipData containing one or more items with content:// URIs. The app should create a note that uses the first attached image as a background image and enter a mode where the user can draw on the with a stylus.