Method and system for generating and rendering a customized dashboard

1. A method for generating and rendering a customized dashboard, the method comprising:

initiating, by an end computing device, a schema-less dashboard canvas through a frontend application that invokes a server-less library, wherein the server-less library comprises a plurality of native widgets and a plurality of adaptors corresponding to a plurality of third-party widgets, and wherein the plurality of third-party widgets is based on one or more different user interface (UI) technologies and one or more different data schemas;

integrating, by the end computing device, a set of widgets selected by a user, from the plurality of native widgets and from the plurality of third-party widgets, with the schema-less dashboard canvas using the server-less library, wherein one or more of the selected third-party widgets from the set of widgets are integrated using one or more corresponding adaptors, and wherein each of the set of widgets is independently configurable by the user to generate the customized dashboard;

generating, by the end computing device, metadata for each of the set of widgets based on a corresponding configuration performed by the user, wherein the metadata comprise a set of unique widget properties; and

associating, by the end computing device, the metadata with a user account of the user for subsequent rendering of the customized dashboard for the user.

2. The method of claim 1 , further comprising, at least one of:

registering, by the end computing device, each of the plurality of third-party widgets with the schema-less dashboard canvas, wherein registering comprises updating the server-less library with an adaptor corresponding to a third-party widget; and

delisting, by the end computing device, one or more of the plurality of third-party widgets from the schema-less dashboard canvas, wherein delisting comprises removing one or more adaptors, corresponding to the one or more of the plurality of third-party widgets, from the server-less library.

3. The method of claim 1 , further comprising:

rendering, by the end computing device, the customized dashboard associated with the user based on the association, through the frontend application.

4. The method of claim 1 , further comprising:

removing, by the end computing device, one or more of the set of widgets from the customized dashboard, wherein removing comprises dissociating or removing the metadata corresponding to the one or more of the set of widgets from the user account.

5. The method of claim 1 , wherein the frontend application comprises at least one of: a standalone application and one or more micro frontend applications, wherein the standalone application comprises the plurality of adaptors, a set of integration protocols, a set of feature extensions, a set of application programming interfaces (APIs), and a set of kernels, and wherein each of the one or more micro frontend applications comprises one or more components, a business logic, and a state management library.

6. The method of claim 5 , wherein the frontend application provides for at least one of: direct integration of one or more of the plurality of third-party widgets, and distributed integration of one or more of the plurality of third-party widgets via a shared event bus.

7. The method of claim 1 , wherein the set of unique widget properties comprises one or more widget identification parameters, one or more widget visualization parameters, one or more widget data schema parameters, one or more widget data security parameters, one or more widget state parameters, and one or more widget rendering components.

8. A system for generating and rendering a customized dashboard, the system comprising:

a processor; and

a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which when executed by the processor, cause the processor to:

initiate a schema-less dashboard canvas through a frontend application that invokes a server-less library, wherein the server-less library comprises a plurality of native widgets and a plurality of adaptors corresponding to a plurality of third-party widgets, and wherein the plurality of third-party widgets is based on one or more different user interface (UI) technologies and one or more different data schemas;

integrate a set of widgets selected by a user, from the plurality of native widgets and from the plurality of third-party widgets, with the schema-less dashboard canvas using the server-less library, wherein one or more of the selected third-party widgets from the set of widgets are integrated using one or more corresponding adaptors, and wherein each of the set of widgets is independently configurable by the user to generate the customized dashboard;

generate metadata for each of the set of widgets based on a corresponding configuration performed by the user, wherein the metadata comprise a set of unique widget properties; and

associate the metadata with a user account of the user for subsequent rendering of the customized dashboard for the user.

9. The system of claim 8 , wherein the processor instructions, on execution, further cause the processor to, at least one of:

register each of the plurality of third-party widgets with the schema-less dashboard canvas, wherein registering comprises updating the server-less library with an adaptor corresponding to a third-party widget; and

delist one or more of the plurality of third-party widgets from the schema-less dashboard canvas, wherein delisting comprises removing one or more adaptors, corresponding to the one or more of the plurality of third-party widgets, from the server-less library.

10. The system of claim 8 , wherein the processor instructions, on execution, further cause the processor to:

render the customized dashboard associated with the user based on the association, through the frontend application.

11. The system of claim 8 , wherein the processor instructions, on execution, further cause the processor to:

remove one or more of the set of widgets from the customized dashboard, wherein removing comprises dissociating or removing the metadata corresponding to the one or more of the set of widgets from the user account.

12. The system of claim 8 , wherein the frontend application comprises at least one of: a standalone application and one or more micro frontend applications, wherein the standalone application comprises the plurality of adaptors, a set of integration protocols, a set of feature extensions, a set of application programming interfaces (APIs), and a set of kernels, and wherein each of the one or more micro frontend applications comprises one or more components, a business logic, and a state management library.

13. The system of claim 12 , wherein the frontend application provides for at least one of: direct integration of one or more of the plurality of third-party widgets, and distributed integration of one or more of the plurality of third-party widgets via a shared event bus.

14. The system of claim 8 , wherein the set of unique widget properties comprises one or more widget identification parameters, one or more widget visualization parameters, one or more widget data schema parameters, one or more widget data security parameters, one or more widget state parameters, and one or more widget rendering components.

15. A non-transitory computer-readable medium storing computer-executable instructions for generating and rendering a customized dashboard, the computer-executable instructions configured for:

initiating a schema-less dashboard canvas through a frontend application that invokes a server-less library, wherein the server-less library comprises a plurality of native widgets and a plurality of adaptors corresponding to a plurality of third-party widgets, and wherein the plurality of third-party widgets is based on one or more different user interface (UI) technologies and one or more different data schemas;

integrating a set of widgets selected by a user, from the plurality of native widgets and from the plurality of third-party widgets, with the schema-less dashboard canvas using the server-less library, wherein one or more of the selected third-party widgets from the set of widgets are integrated using one or more corresponding adaptors, and wherein each of the set of widgets is independently configurable by the user to generate the customized dashboard;

generating metadata for each of the set of widgets based on a corresponding configuration performed by the user, wherein the metadata comprise a set of unique widget properties; and

associating the metadata with a user account of the user for subsequent rendering of the customized dashboard for the user.

16. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions are further configured for, at least one of:

registering each of the plurality of third-party widgets with the schema-less dashboard canvas, wherein registering comprises updating the server-less library with an adaptor corresponding to a third-party widget; and

delisting one or more of the plurality of third-party widgets from the schema-less dashboard canvas, wherein delisting comprises removing one or more adaptors, corresponding to the one or more of the plurality of third-party widgets, from the server-less library.

17. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions are further configured for:

rendering, by the end computing device, the customized dashboard associated with the user based on the association, through the frontend application.

18. The non-transitory computer-readable medium of claim 15 , wherein the computer-executable instructions are further configured for:

removing, by the end computing device, one or more of the set of widgets from the customized dashboard, wherein removing comprises dissociating or removing the metadata corresponding to the one or more of the set of widgets from the user account.

19. The non-transitory computer-readable medium of claim 15 , wherein the frontend application comprises at least one of: a standalone application and one or more micro frontend applications, wherein the standalone application comprises the plurality of adaptors, a set of integration protocols, a set of feature extensions, a set of application programming interfaces (APIs), and a set of kernels, and wherein each of the one or more micro frontend applications comprises one or more components, a business logic, and a state management library.

20. The non-transitory computer-readable medium of claim 19 , wherein the frontend application provides for at least one of: direct integration of one or more of the plurality of third-party widgets, and distributed integration of one or more of the plurality of third-party widgets via a shared event bus.