Input matters for Chrome OS

on YouTube ↗17m

" summary

Concrete fixes and examples guide decisions: add explicit keyboard handling by overriding onKeyUp to handle Enter and return true, add MIDI support using Android Media Samples or NDK MIDI, replicate EDJing’s approach of keyboard mappings and trackpad scratching to reuse existing hardware, use a lazy state machine with a 5-second delay to switch UI prompts between touch keyboard and controller, implement pointer capture to hide the cursor during scratching, and try the low-latency stylus API now available in alpha.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 0:19Devices galore!
3. 9:51Lazy state machine
4. 12:14Gamepad mappings
5. 13:30Pointer Capture
6. 15:22Stylus input
7. 15:50Low-latency API

" related talks

• 20mWin the hearts of Chrome OS users with AndroidFrédéric Torcheux, Pierre Issartel · Android Makers 2022
• 18mThe key to keyboard and mouse support across tablets and ChromeOSMiguel Montemayor, Gina Domergue · Android Dev Summit 2022
• 18mThe key to keyboard and mouse support across tabletsMiguel Montemayor, Gina Domergue · Android Dev Summit 2022: Form Factors
• 29mMIDI A New Dimension in Controlling Your BrowserArmagan Amcalar · You Gotta Love Frontend 2019
• 15mInput for all screensPatrick Fuentes · Google I/O 2022
• 41mWhat’s new in Android apps for Chrome OSStefan Kuhne, Shahid Hussain · Google I/O 2018
• 16mDeveloping for Android & large screensKenneth Ford · Android Dev Summit 2018
• 36mBuilding Android apps for the Chrome OS ecosystemEmilie Roberts, Stefan Kuhne, Sweet Song · Google I/O 2019