...
The idea is to not tie this to ERM in any meaningful way. This way any build can potentially make use of this service/app, and we can attempt to have have cohesion and similarity of design no matter which users are using this app, and which module's widgets they're attempting to add to their dashboard.
As part of this we aim to build a system where new definitions can be added automatically by other modules, requiring absolutely zero work from our team. Simply send your Definitions for a Type and see your widgets appear as options in your system.
We hope the backend module mod-service-interaction can become a storage point for certain frontend information, allowing this kind of inter-app interaction as smoothly as possible for both the dashboard, and also any other apps which need this information.
Finally, with all of the components for ui-dashboard we are aiming to be as simple and reusable as possible. A good example is the DragAndDropFieldArray, which we have designed not just for our specific use case, but to work in general anywhere it would be useful to reorder a FieldArray within a FinalForm component. With these we hope to provide both a useful frontend app, but also tools and patterns other frontend developers can use within their own builds.