I have made use of TouchWrappers in a sequence of buttons to present a number of actions to the user, when the user presses a button, it sends an event to the server and acts as if the user had said the action.
I have three issues with this current implementation:
1. Currently, there is no indication on the device that the user has pressed the button, is there a way to provide a frontend response showing to the user the button has been pressed and their action is being handled?
2. The lack of responsiveness from the buttons leads to users repeatedly pressing the buttons which results in numerous events being sent to the Lambda function. These numerous events mean more than one response being sent to the user. Is there a way to limit the amount of events which can be sent from a wrapper? (i.e. don't send anymore events after it has been pressed once)
3. Finally, I have noticed differences between the simulator and device in the arguments sent in the APL User Event Request, specifically the data (the selected list item) sent by the simulator is an object, where as the device sends a Stringified object.