Hey @Skiks I’m wondering if you might have a perspective - in a notebook context - of when/where use of ipywidgets might be “best” and when/where (jupyter)dash might be “best” … where overlap is / etc … there’s obviously lots of options in a notebook for simpler dashboards/EDA/etc workflows … and Dash admittedly is differentiated when you want to do more sophisticated web apps and ipywidgets gets a lot of downloads … so keen to provide best steer when the topic comes up on my end.
To be honest, I’m not a huge fan of notebooks, I fell like kind of claustrophobic in their little cells
Joke aside, I quickly learnt how to use Jupyter notebooks as it is a popular tool, and as I expected, I think it is more for educational purposes, to show, explain, teach or quick snippets testing, typically EDA, but I find notebooks too restrictives.
That being said, if I must compare ipywidgets vs jupyter_dash:
Ipywidgets:
Easier to use
Provide quickly controls to add interactivity
Limited customization, styling
jupyter_dash:
More controls/components = more interactivity options
Almost everything is customizable, style, behavior, layout
More complex to use?
In conclusion I would say that ipywidgets is a better match to notebooks, to quickly and easily try codes and show simple demos adding interactivity.
On the other hand, jupyter_dash offers the possibility to use Dash in notebooks, always nice to have the choice, but I think it is not the purpose of notebooks to have nice styled customized outputs with complex interactivity.
If the goal is the latter, and using a notebook is not a constrain, I think it is better to break the cells and unleash all the power of Dash !