Description of App and Sketch

[danfke]

Building from your research questions and usage scenarios, give a high-level description of the interface for the app you will build. Remember to be realistic about your expectations and plans since you will actually be implementing this app (but again, you will not be penalized if you need to adjust a bit in later milestones). It is better to design a slightly more limited app that you have time to implement well, instead of a complicated app that you don’t have time to finish. At the same time, you cannot just make a single barchart and call it a day. The app needs to have a few plot panels, use the visualizations from previous students as a guide as a complexity target for the final app.

In this description you are not required to use terminology specific to Dash apps (i.e. widgets, components, etc…) or make reference to specific Python or R libraries. Your sketch can be hand-drawn or mocked up using a graphics editor. If you can show the app visual design & interaction design in a single image that is ideal, but if you need more space to show some other planned features of your app you can include max three images for this proposal.

The description should be about 200-300 words and live in the README.md file of your GitHub.com repository. The sketch should be linked in the README.md file of your GitHub.com repository underneath the high level description so that the image shows up on GitHub.

[scarlqq]

A sketch based on our discussion ... a very very basic one, just an idea :)

[danfke]

Looks nice QingQing! I was also thinking it would be cool to somehow incorporate a plot on stressors but I agree that three plots is probably the way to go. I'm not sure if a calendar makes sense to select the data in this case, because we only have data for quarters. I'm experimenting with different colour palettes to aim for more of a bee theme

[danfke]

Maybe something along this colour palette: