Sounds like this app requires a touchscreen: see https://developer.android.com/topic/arc/index.html

Sergey, can you PTAL?

This have nothing to do with kiosk feature as per description the app doesn't work in general on ChromeOS.

Assigning to Elijah to provide more details on whether 'android.app.touchscreen' feature should be turned on if such touchscreen device is attached to a Chromebox.

Current state seems to be that 
android.hardware.touchscreen is not available but android.hardware.faketouch is set.

Main question probably is, is android.hardware.touchscreen supposed to be enabled when external monitor is capable of touch ? 

c.f. 
https://developer.android.com/guide/topics/manifest/uses-feature-element.html 

does not quite say anything about when things are externally pluggable. (features is something fairly static)

We support feature detection at runtime (go/arc-board-features) but there are two questions: 1. is that external touchscreen supported by chromeos? it may not work if we don't have proper drivers. 2. external devices must be probed in the board feature detection script.

+bhthompson

Hi Bernie, do you know if we have some support plan for such case (external touchscreen on chromebox)?

We only attempt to detect internal touch screens, so having a box that is connected to an external touch screen is not currently expected to expose that touch capability.

Since we cannot guarantee the touch screen is always there, we cannot expose the feature, by some interpretations of the Android CDD.

Since this is dynamic, we might be able to do better probing and expose the touch screen feature if a USB touch screen is detected at boot? We probably need to research more internally on how to interpret the CDD in such a case.