Systems And Methods For Measurement Of Unsupported User Interface Actions

1. A method, comprising: receiving, by an application hosted on a computing device, a user interface event at a user interface of the application, wherein the application uses an event handling hierarchy of an unsupported event module and event handlers, wherein the unsupported event module is installed in the application as a plug-in; determining, by the unsupported event module, whether any of the event handlers is capable of supporting the user interface event; in response to determining that the event handlers are incapable of handling the user interface event, identifying, by the unsupported event module, that the user interface event is an unsupported event, wherein operations of the user interface of the application are unaffected by the unsupported event; generating, by the unsupported event module, one or more records comprising information about the user interface event and an indication that the user interface event is unsupported; and storing, by the unsupported event module, the one or more records at the computing device; transmitting the one or more records from the computing device to a collection server; and modifying the application on the computing device based on an analysis of the one or more records and of a plurality of records collected at the collection server and associated with instances of the application on a plurality of computing devices, the modifying comprising an update to the event handling hierarchy to include an event handler configured to handle the user interface event and support an additional operation of the application corresponding to the user interface event.

2. The method of claim 1 , wherein the application does not respond to user interface events identified as unsupported.

3. The method of claim 1 , wherein said recording comprises: recording an event type for the user interface event; and recording an event context for the user interface event.

4. The method of claim 3 , wherein the event context comprises one or more screen coordinates of the user interface event, window coordinates of the user interface event, page coordinates of the user interface event, user interface view for the user interface event, or user interface element for the user interface event.

5. The method of claim 1 , further comprising recording, during execution of the application, usage metrics data for the application, wherein the usage metrics data comprise one or more of visitor or user identifier, page views, visits, or time spent on view.

6. The method of claim 1 , wherein the user interface event comprises one or more of: touch screen event, mouse click event, keyboard event, device movement event, or voice command event.

7. The method of claim 1 , wherein the application comprises an event handling system in which events are propagated through the event handling hierarchy such that user interface events not supported at one event level of the hierarchy are passed to a next level, and wherein identifying the user interface event as unsupported is determined by identifying that the next level and a parent level of the next level are not configured to support the user interface event.

8. The method of claim 1 , further comprising: determining one or more user interaction levels that are not configured to support the user interface event; and wherein the recording comprises: recording the one or more user interaction levels.

9. The method of claim 1 , wherein the unsupported event module is at an end of the event handling hierarchy.

10. The method of claim 1 , wherein the collection server is configured to generate a report based on the one or more records and the plurality of records, wherein the report is configured to provide metrics about the user interface event at different user-selectable granularity levels.

11. The method of claim 1 , wherein the user interface event is received at a location on the user interface corresponding to a user interface object, wherein the determining that the event handlers are incapable of supporting the user interface event comprises determining, by the unsupported event module, that no event handler is attached to the user interface object for the user interface event.

12. The method of claim 1 , wherein each of the event handlers and the unsupported event module is at a different level of the event handling hierarchy, wherein the plug-in installs the unsupported event module in the event handling hierarchy, and wherein the operations of the user interface are unaffected by the unsupported event by at least propagating the user interface event through the event handling hierarchy and not changing the user interface based on the user interface event being identified as an unsupported event by the unsupported event module.

13. A method, comprising: receiving, from a plurality of remote computing devices, user interface event records of user interface events recorded during use of respective instances of an application on the plurality of remote computing devices, wherein: the recorded user interface events are user interface events that the application flags as unsupported by using an event handling hierarchy, the event handling hierarchy comprises event handlers and an unsupported event module, the event handlers are configured to handle events based on corresponding event levels, the unsupported event module is installed as a plug-in to the application and is configured to identify the user interface events as unsupported based on determinations by the unsupported event module whether any of the event handlers is capable of handling the user interface events, and operations of a user interface of the application are unaffected by the user interface events being unsupported by the application; aggregating the user interface event records for the application; and generating a report, based on the aggregated user interface event records for the application, the report usable to modify the application such that an instance of the application on at least one of the plurality of computing devices is updated to include, in the event handling hierarchy, an event handler configured to handle at least one of the user interface events and support an additional operation of the application corresponding to the user interface event.

14. The method of claim 13 , further comprising receiving usage metric data, from the plurality of remote computing devices, for the respective instances of the application on the plurality of remote computing devices.

15. The method of claim 14 , wherein the usage metrics data comprises visitor identifiers or user identifiers for each remote computing device or instance of the application.

16. The method of claim 15 , wherein said generating a report comprises determining a number of unsupported user interface action attempts per user or visitor.

17. The method of claim 16 , wherein said determining a number of unsupported user interface action attempts per user or visitor is performed for each of a plurality of user interface events, wherein said generating a report comprises generating a ranked list or table of the unsupported user interface action attempts not supported by the application ranked according to a percentage of unsupported user interface action attempts per user or visitor.

18. The method of claim 13 , wherein the application is not configured support comprise one or more of: touch screen event, mouse click event, keyboard event, device movement event, or voice command event.

19. The method of claim 13 , wherein a user interface event record of the user interface event comprises user interaction levels that are not configured to support the user interface event.

20. A system, comprising: a processor; and a memory storing an unsupported events module executable by the processor to: identify a user interface event received by an application as unsupported by using an event handling hierarchy, wherein: the event handling hierarchy comprises event handlers and an unsupported event module, the event handlers are configured to handle events based on corresponding event levels, the unsupported event module is installed as a plug-in to the application and is configured to identify the user interface event as unsupported based on a determination by the unsupported event module whether any of the event handlers is capable of handling the user interface, and operations of a user interface of the application are unaffected by the user interface events being unsupported by the application; record, by the unsupported event module, one or more records with information of user interface events that indicate the user interface event and that the user interface event is unsupported; store or transmit, to a server, the one or more records; and modify the application on the system based on an analysis of the one or more records, the modification comprising an update to the event handling hierarchy to include an event handler configured to handle the user interface event and support an additional operation of the application corresponding to the user interface event.

21. The system of claim 20 , wherein the user interface event comprises one or more of: touch screen event, mouse click event, keyboard event, device movement event, or voice command event.

22. The system of claim 20 , wherein the application does not respond to the user interface event recorded by the unsupported event module.

23. The system of claim 20 , wherein said record comprises: record an event type for the user interface event; and record an event context for the user interface event.

24. The system of claim 23 , wherein the event context comprises one or more of a screen coordinates of the user interface event, window coordinates of the user interface event, page coordinates of the user interface event, user interface view for the user interface event, or user interface element for the user interface event.

25. The system of claim 20 , wherein the application comprises an event handling system in which events are propagated through the event handling hierarchy such that user interface events not supported at one event level of the hierarchy are passed to a next level, and wherein identifying the user interface event as unsupported is determined by identifying that the next level and a parent level of the next level are not configured to support the user interface event.

26. A non-transitory computer readable storage medium storing computer-executable program instructions that when executed by a computer are configured to cause: installing one or more unsupported event handlers as a plug-in to an application, wherein: the one or more unsupported event handlers are configured to only receive user interface events not handled by supported event handlers of the application and to determine whether any of the supported event handlers is capable of handling the user interface events, the one or more unsupported event handlers and the supported event handlers are arranged in an event handling hierarchy, operations of a user interface of the application are unaffected by the user interface events not being handled by the supported event handlers; during execution of the application, recording, by the one or more unsupported event handlers, user interface events not handled by the application; storing or transmitting one or more records of the user interface events recorded by the one or more unsupported event handlers; and modifying the application on the computer based on an analysis of the one or more records, the modifying comprising an update to the event handling hierarchy to include a supported event handler configured to handle at least one of the user interface events and support an additional operations of the application corresponding to the user interface events.

27. The medium of claim 26 , wherein said installing the one or more event unsupported handlers comprises installing the plug-in to the application.

28. The medium of claim 26 , wherein said recording comprises: recording an event type for each of the user interface events not handled by the application; and recording an event context for each of the user interface events not handled by the application.

29. The medium of claim 28 , wherein the event context comprises one or more of a screen coordinates of the user interface event, window coordinates of the user interface event, page coordinates of the user interface event, user interface view for the user interface event, or user interface element for the user interface event.

30. The medium of claim 26 , further comprising recording, during execution of the application, usage metrics data for the application, wherein the usage metrics data comprise one or more of visitor or user identifier, page views, visits, or time spent on view.

31. The medium of claim 26 , wherein the user interface events not handled by the application comprise one or more of: touch screen event, mouse click event, keyboard event, device movement event, or voice command event.

32. The medium of claim 26 , wherein said storing or transmitting one or more records comprises transmitting the one or more records to a collection server.

33. The medium of claim 26 , wherein the application comprises an event handling system in which events are propagated through the event handling hierarchy such that user interface events not handled at one level of the hierarchy are passed to a next level, wherein said installing the one or more unsupported event handlers comprises installing the one or more unsupported event handlers at an end of the hierarchy so that user interface events not handled by the application are recorded by the one or more unsupported event handlers.