Automated kitting for Android dedicated devices using WebADB
summary
Presents a system to convert Android devices into single-purpose terminals by automating ADB commands either with shell scripts or via a browser client using WebADB over WebUSB (frontend in TypeScript/Next.js, hosted on Google Cloud, Chrome-only). The shell-script flow reduces manual engineer setup from over an hour to one automated run, while the WebADB demo lets a phone or PC control a device without installing ADB. Describes robustness improvements: timed retries, corrected touch-coordinate handling, and a fallback that uses the Accessibility Services API to locate and tap UI elements.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:29What is kitting
- 5:18Manual kitting challenges
- 9:57Automating kitting
- 12:10Shell script kitting tool
- 19:05Improving kitting tool
- 23:00Need for web app
- 23:22WebADB mechanism
- 26:44WebADB implementation
- 31:26WebADB kitting benefits
- 31:48Summary
- 33:19Accessibility API usage
- 37:48Kitting tool potential
related talks
57mAutomating Android: Command line controls
21mWhat if ADB does not have to be that complicated?
45mPractical ADB usage to enhance your life!
39mPractical ADB usage to enhance your life!
40mPractical ADB usage to enhance your life!
38mBring your own phones to Gradle Managed Devices
20mLife is too short not to use ADB commands
42mADB Break on through to the other side