When running tests on the Chrome browser on Android through the Appium UiAutomator2 engine, the current behavior initiates a whole series of actions to determine the installed version of Chrome on the device, verify that a compatible driver is installed, and download a driver if it's missing. This takes quite a bit of time, but this overhead can be eliminated by specifying the path to a compatible pre-installed driver. This is specified through the appium:chromedriverExecutable capability.
The objective is to eliminate unnecessary invocations of adb, which Appium uses to query the version of Chrome that's installed.