Audience matters:
You’ve done a great job at understanding the potential audience for your dashboard and you’ve made an application that would be well-suited to someone who enjoys drinking wine. I like that you inform the user of how the data was acquired and how the data may be useful, as well as how to use the app.
Choose defaults wisely:
I think the defaults that you went with in the app were well-chosen. California is a great choice for the map as it seems to have the most wineries. Fifteen observations for the histogram was also a smart choice as it’s informative and not too crowded. Finally, showing ‘Price” as the default for the heatmap was good because most users are probably more interested in the price of a wine rather than its rating.
Aesthetics matter:
You’ve gone all out here. The color scheme, the maps, and the layout are all incredibly impressive. I especially like the watermark in the Jumbotron and the favicon. The name of the dashboard is also terrific (much better than W is for Wino). The only (small) drawback in terms of aesthetics is that when the user selects the maximum number of observations for the histogram, the x-axis gets a little crowded. I would think about not letting the user select that many observations, but this isn’t a major problem. The layout and aesthetics are very consistent.
Think about the “onboarding” experience:
Overall really well done. As I mentioned earlier, the opening summary is a good introduction to the dashboard and I don’t think any user would have problems navigating the site. The graphs themselves are very easy to use and informative. One thing I noticed was that the heatmap is a little hidden below the histogram so I worry that some unobservant users might miss out on it. The heatmap also takes a while to update when you change from rating to price, so a little note to inform to user that it might take some time when changing variables could be a good idea.
Audience matters: You’ve done a great job at understanding the potential audience for your dashboard and you’ve made an application that would be well-suited to someone who enjoys drinking wine. I like that you inform the user of how the data was acquired and how the data may be useful, as well as how to use the app.
Choose defaults wisely: I think the defaults that you went with in the app were well-chosen. California is a great choice for the map as it seems to have the most wineries. Fifteen observations for the histogram was also a smart choice as it’s informative and not too crowded. Finally, showing ‘Price” as the default for the heatmap was good because most users are probably more interested in the price of a wine rather than its rating.
Aesthetics matter: You’ve gone all out here. The color scheme, the maps, and the layout are all incredibly impressive. I especially like the watermark in the Jumbotron and the favicon. The name of the dashboard is also terrific (much better than W is for Wino). The only (small) drawback in terms of aesthetics is that when the user selects the maximum number of observations for the histogram, the x-axis gets a little crowded. I would think about not letting the user select that many observations, but this isn’t a major problem. The layout and aesthetics are very consistent.
Think about the “onboarding” experience: Overall really well done. As I mentioned earlier, the opening summary is a good introduction to the dashboard and I don’t think any user would have problems navigating the site. The graphs themselves are very easy to use and informative. One thing I noticed was that the heatmap is a little hidden below the histogram so I worry that some unobservant users might miss out on it. The heatmap also takes a while to update when you change from rating to price, so a little note to inform to user that it might take some time when changing variables could be a good idea.