Data collection visualization facility for creating three-dimensional user interfaces

1. A computer-implemented method,

comprising:

presenting, by at least one processor of a mobile device, a set of available visualization components in a browser, wherein the set of available visualization components are stored on the mobile device;

setting, by the at least one processor, data adaptor information of a selected visualization component in an application, wherein the data adaptor information comprises:

a data structure for the application to display the selected visualization components as a user-interface object, and

a data source from which to retrieve detail data associated with the selected visualization component,

wherein the data adaptor information is configured to be retrieved by a data exchange adaptor, and

wherein the data exchange adaptor is configured to retrieve the detail data from the data source;

and

invoking, by the at least one processor; an event handler configured to cause the selected visualization component to perform operations comprising:

receiving the detail data from the data exchange adaptor or from the data source, and

rendering the user-interface object on a display, wherein the rendering is based on the data adaptor information of the selected visualization component, and wherein the rendering is further based on the detail data received.

2. The method of claim 1 , further comprising:

defining, by the at least one processor, one or more parameters associated with the visualization component.

3. The method of claim 2 , wherein the one or more parameters include visualization type, item, the data exchange adaptor, and the event handler.

4. The method of claim 1 , further comprising:

executing, by the at least one processor, the application on a mobile client device; and

executing, by the at least one processor, an event defined by the event handler associated with the visualization component when an action on the rendered visualization component is detected.

5. The method of claim 4 , further comprising:

retrieving, by the at least one processor, event data associated with the visualization component when the event is executed.

6. The method of claim 5 , wherein the retrieving further comprising:

retrieving, by at least one processor, the event data associated with the visualization component from at least one of a local database and a remote database.

7. The method of claim 1 , further comprising:

defining, by the at least one processor, a security protocol used for retrieving data associated with the visualization component.

8. The method of claim 1 , wherein the user interface object comprises a three-dimensional (3D) user interface object.

9. The method of claim 1 , wherein the visualization component is configured to be defined by a developer, an end user, or both.

10. A system comprising:

a memory at a mobile device; and

at least one processor at the mobile device coupled to the memory and configured to:

present a set of available visualization components in a browser, wherein the set of available visualization components are stored on the mobile device;

set data adaptor information of a selected visualization component in an application, wherein the data adaptor information comprises:

a data structure for the application to construct the selected visualization component as a user-interface object, and

a data source from which to retrieve detail data associated with the selected visualization component,

wherein the data adaptor information is configured to be retrieved by a data exchange adaptor, and

wherein the data exchange adaptor is configured to retrieve the described data structure from the data source;

and

invoke an event handler configured to cause the selected visualization component to perform operations comprising:

receiving the detail data from the data exchange adaptor or from the data source, and

rendering the user-interface object on a display, wherein the rendering is based on the data adaptor information of the selected visualization component, and wherein the rendering is further based on the detail data received.

11. The system of claim 10 , the at least one processor further configured to:

define one or more parameters associated with the visualization component.

12. The system of claim 11 , wherein the one or more parameters include visualization type, item, the data exchange adaptor, and the event handler.

13. The system of claim 10 , the at least one processor further configured to:

execute the application on a mobile client device; and

execute an event defined by the event handler associated with the visualization component when an action on the rendered visualization component is detected.

14. The system of claim 13 , the at least one processor further configured to:

retrieve event data associated with the visualization component when the event is executed.

15. The system of claim 14 , wherein to retrieve the at least one processor is configured to:

retrieve the event data associated with the visualization component from at least one of a local database and a remote database.

16. The system claim 9 , the at least one processor further configured to:

define a security protocol used for retrieving data associated with the visualization component.

17. The system of claim 10 , wherein the user interface object comprises a three-dimensional (3D) user interface object.

18. The system of claim 10 , wherein the visualization component is configured to be defined by a developer, an end user, or both.

19. A non-transitory computer-readable storage medium having instructions stored thereon that, when executed by at least one computing device of a mobile device, causes the at least one computing device to perform operations comprising:

presenting, by at least one processor of a mobile device, a set of available visualization components in a browser, wherein the set of available visualization components are stored on the mobile device;

setting data adaptor information of a selected visualization component in an application, wherein the data adaptor information comprises:

a data structure for the application to construct the selected visualization component as a user-interface object, and

a data source from which to retrieve detail data associated with the selected visualization component,

wherein the data adaptor information is configured to be retrieved by a data exchange adaptor, and

wherein the data exchange adaptor is configured to retrieve the described data structure from the data source;

and

invoking an event handler configured to cause the selected visualization component to perform operations comprising:

receiving the detail data from the data exchange adaptor or from the data source, and

rendering the user-interface object on a display, wherein the rendering is based on the data adaptor information of the selected visualization component, and wherein the rendering is further based on the detail data received.

20. The non-transitory computer-readable storage medium of claim 19 , the operations further comprising:

defining one or more parameters associated with the visualization component, wherein the one or more parameters include visualization type, item, the data exchange adaptor, and the event handler.

21. The non-transitory computer-readable storage medium of claim 19 , the operations further comprising:

executing the application on a mobile client device;

executing an event defined by the event handler associated with the visualization component when an action on the rendered visualization component is detected; and

retrieving event data associated with the visualization component when the event is executed.

22. The non-transitory computer-readable storage medium of claim 21 , wherein the retrieving further comprising:

retrieving the event data associated with the visualization component from at ast one of a local database and a remote database.

23. The non-transitory computer-readable storage medium of claim 19 , wherein the user interface object comprises a three-dimensional (3D) user interface object.

24. The non-transitory computer-readable storage medium of claim 19 , wherein visualization component is configured to be defined by a developer, an end user, or both.