In early 2019 MRTK already supported a wide variety of input devices (including hands, voice, touch screens and controllers). However, developers were required to implement specific handlers for each type of input. For example, specific code would have to be written to handle a spoken phrase and additional code would have to be written to handle a controller button even if they performed the same action. Jared worked with the MRTK team to define an approach for mapping any input source to any action, greatly reducing the code necessary for common scenarios.
Contributors: Jared Bienz