Vancouver Cherry blossom tracker - Group 25

[ytz]

To complete by the group

• Name of the app: Vancouver Cherry blossom tracker
• Link to the repo in milestone2: https://github.com/UBC-MDS/cherry_blossom_tracker/releases/tag/1.0.0
• Link to the proposal.md file where it is the description of the persona and scenario: https://github.com/UBC-MDS/cherry_blossom_tracker/blob/main/docs/proposal.md

---

2. Review the group that is one number ahead of your group's number. For example, if you are group 5, review group 6. If you are group 30, review group 1. Paste your answers in the issue of the group assigned.

---

To complete by the group reviewing:

Persona

• Provide 3 pieces of constructive feedback that could help the app to be better suited to the scenario it was designed for
• Provide 3 pieces of constructive feedback that could help the app to be better suited to the user(persona) it was designed for

Frontend / layout

• Is the text (plot labels / titles / subtitles) easy to read?
• Are the plots selected appropiated for the data? Can you think of other alternatives or improvements for the plots regarding interactivity/reactivity or plot selection?
• Was the dashboard organized in a way that was easy to read (columns / rows) or you would suggest a change in this sense?
• Would you prefer including tabs / navbars to improve the navigation or you think it is better to visualize everything in one screen by the nature of the content?
• Are the plots or other images described properly for the persona described?

Backend

• Are the options that you can select in the widgets working fine or have you found some cases where it is not working?
• If there are interactive plots: are the labels clear and easy to understand?

Documentation

• Was the documentation easy to understand from the README.md how to use the app? How could the documentation be improved?
• Was the app intuitive to use without reading the documentation? What information could be good to include?

Indicate something you would like to include in your own app after reviewing this one

---

[ming0701]

Reviewer: Group 24 Persona • Provide 3 pieces of constructive feedback that could help the app to be better suited to the scenario it was designed for

1. For your scenario, the users (tourists) may want to compare different neighbourhoods and tree types, it would be nice to allow multiple selection in the filters.
2. Tourists may want to visit the place with most trees on selected dates, you may consider adding a chart of top 10 places to visit ranked by number of trees with date as filter.
3. For the tree density chart, tourists may also be interested in tree diameters by tree type. You may consider providing the breakdown by tree type for this chart.

• Provide 3 pieces of constructive feedback that could help the app to be better suited to the user(persona) it was designed for

1. Since Tom is interested in the biggest trees, you may consider adding a chart with top 10 trees (ranked by diameter, date, neighbourhood and tree type filters can be applied), so that he can identify those trees easily.
2. Tom may be interested to know the average tree diameters of the neighbourhood selected, so that he can visit the place with largest tree diameters. You may consider adding the average in the tree diameters plot or in the tooltip of tree density map.
3. The overall color scheme looks good, but it would be easier for Tom to classify if the plots are in different colors by categories (e.g. tree type).

Frontend / layout • Is the text (plot labels / titles / subtitles) easy to read?

• Yes, the text is easy to read in general
• Unit is missing for the y-axis of the tree diameters chart, not easy to read for the users
• “Count of Records” for the Tree density map can be changed to “Number of trees”

• Are the plots selected appropriated for the data? Can you think of other alternatives or improvements for the plots regarding interactivity/reactivity or plot selection?

• Yes, the plots are appropriate for the data. Regarding the tree diameters density plot, it may easier for the users if it is a bar chart with number of tree as the y-axis.

• Was the dashboard organized in a way that was easy to read (columns / rows) or you would suggest a change in this sense?

• Yes, the dashboard is clean and easy to read.
• I would suggest reducing the size of the map and try to fit everything in one screen so that the users do not need to scroll up and down.

• Would you prefer including tabs / navbars to improve the navigation or you think it is better to visualize everything in one screen by the nature of the content?

• It is better to visualize everything in one screen so that the users can refer to other plots and map at the same time.

• Are the plots or other images described properly for the persona described?

• Yes in general.
• As mentioned above, the density chart may not be easy / direct for the user.
• The user may also want to select multiple neighbourhoods and tree cultivars in the filters.

Backend • Are the options that you can select in the widgets working fine or have you found some cases where it is not working?

• Everything works well.

• If there are interactive plots: are the labels clear and easy to understand?

• It would be better if you show a more readable label instead of the column name (e.g. “common_name”, “neighbourhood_name”) in the tooltip of the maps

Documentation • Was the documentation easy to understand from the README.md how to use the app? How could the documentation be improved?

• The documentation is easy to understand. Great to have the gif added, but it would be better if more functionalities (e.g. using the filters and sliders, showing tooltip when you hover over the plots) can be demonstrated in the gif.