Currently the requirements file includes all the dependencies required to run both the AR app and the data visualization app. Furthermore, some of the data visualization dependencies are quite heavy (Flask, Plotly or Dash).
I think it makes sense to split the requirements in two parts (AR on one side and data visualization on the other side) so that users who only want to tinker with the AR code don't install packages that will not be used.
Currently the requirements file includes all the dependencies required to run both the AR app and the data visualization app. Furthermore, some of the data visualization dependencies are quite heavy (Flask, Plotly or Dash).
I think it makes sense to split the requirements in two parts (AR on one side and data visualization on the other side) so that users who only want to tinker with the AR code don't install packages that will not be used.
Additional info: Customize a requirements.txt for multiple environments