maxschulz-COL
We are definitely taking these points into consideration.
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.
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 Dash and e.g. Streamlit (given that it has been mentioned on this thread); it leverages the simplicity and low-code solution approach of something like Streamlit, but it still enables users the flexibility to customize advanced solutions similar to Dash. Compared to Dash, it keeps configurations simple even if you create more sophisticated actions/callbacks. It comes with an out-of-the box sophisticated look and feel. That being said there are of course reasons to use either of the above mentioned tools, we love them too :).
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