| > In other words, is this for quick one-off visualizations, or can you see someone wanting to use it to build a fully-functional web application? I don't think that Dash will replace standard CRUD style websites. It's more for the visualization and data-science space. The main limitation with Dash is that every interaction has to be through components with pre-named IDs. That means that Dash doesn't support apps that need to bind interactivity or updates on an arbitrary number of items (for example, a TODO app with `N` number of items where each item can be modified). In traditional websites, this is handled through URL patterns, query strings, or client-side through JavaScript. Eventually, Dash might have the abstraction of "ID groups" or "ID patterns", but it doesn't have that quite yet. This type of application is common in standard CRUD websites, less common in data-viz applications or dashboards. In the visualization space, Dash is for both the one-off visualizations (e.g. add a dropdown to a graph) as well as more complex applications that have drill down and search that you might commonly see in something like Tableau. Some examples: - quick one-off visualization: https://plot.ly/dash/gallery/stock-tickers/ - more complex drill down example: https://plot.ly/dash/gallery/new-york-oil-and-gas - the dash userguide website is itself a dash app: https://plot.ly/dash - a dash app styled like a traditional report: https://plot.ly/dash/gallery/goldman-sachs-report/ |