Skip to content

Chrome 158 brings WebHID to Android, no API changes needed

Sites that already use WebHID on desktop, for mechanical keyboards, gamepads and headset controls, now work on Android 17 and later with the same code.

Chrome 158, which reached stable on 17 November, extends the WebHID API to Android. The API itself is unchanged: it has worked on Windows, Mac, Linux and ChromeOS since Chrome 89, and the same navigator.hid.requestDevice() calls now work on a phone or tablet with no code changes.

The catch is the OS underneath. Android needs version 17 (API level 37) or later, since WebHID depends on HID support Chrome’s team added at that OS level. WebView is not supported, Chrome says it lacks the device chooser UI and permissions controls the API needs. Sites that use WebHID today, for calibrating gamepads, remapping mechanical keyboards, or wiring up call-centre headset controls, pick up Android support automatically once a user is on a recent enough phone.

const devices = await navigator.hid.requestDevice({ filters: [] });

Why it matters: if you’ve already built a WebHID integration, there’s nothing to change, your existing site now reaches Android users it couldn’t before. If you were holding off on WebHID because it was desktop-only, that’s no longer true, though you’ll still want a fallback for anyone on an older Android version or inside WebView.

Share

More from The Wire

All briefs