maxschulz-COL

Thank you very much for the feedback!

We are definitely taking these points into consideration.

Thank you for your feedback! I am one of the engineers on team :)

So we introduced this layer to serve as a configuration driven assembly system which implements built-in visual styling and an opinionated approach in terms of both application architecture and UX, in order to enable standardisation in code and user journeys for multi-screen applications and complex interactions between components.

Thank you very much for your feedback! I am one of the engineers on the team. Indeed, what you describe is certainly one of the issues we wanted to address.

Regarding "why Vizro": As we all know it is hard to compare tools like for like, but we see Vizro as a great combination of benefits offered by existing tools (given that some have been mentioned on this thread); it leverages a simplicity and low-code solution approach, but it still enables users the flexibility to customize advanced solutions. It keeps configurations simple even if you create more sophisticated actions/callbacks. It comes with an out-of-the box sophisticated look and feel.

The approach of using a configuration layer to enforce standardisation in the way that components and code is assembled utilises a grammar which is largely tech agnostic, and while it is currently optimised to leverage Plotly and Dash, it could theoretically utilise components from other packages such as StreamLit in future

Thanks a lot for your feedback :) Let us know what you think, we appreciate all feedback!