twoolf / circator

Metabolic Compass: A Circadian Monitoring Mobile Health Stack
https://www.metaboliccompass.com
Apache License 2.0
6 stars 1 forks source link

colors on first dashboard and correlation of colors there to 2nd dashboard #59

Open twoolf opened 8 years ago

twoolf commented 8 years ago

Possibly due to my color blindness, but there's no obvious connection that I see between the color ranges used for the metrics on the first dashboard and the colors for the balance plot on the 2nd dashboard.

It might make more sense to let the user color code the first screen to reflect those of most importance to them (say first seven), then of 2nd-ary importance, and then the remaining, that would then reflect some meaning to the colors. Those first importance metrics (same color) could then be used on the 2nd screen. This is similar to what we used before.

Right now they may have been mapped to our initial choices for each row (when only one selection per color was being used). But, with all the metrics being displayed, it feels awkward to my eye to have so much variation in color without a meaning behind it.

I'm also voting for trying to decrease the number of entries on that first screen -- I just don't think that we've got people wanting to see all of the metrics each time they engage with the App --

conny-the-unicorn commented 8 years ago

@twoolf 1) as for colors correlation between Dashboard and Balance screen. I must assure you, that we are using totally the same colors for each metric mentioned on both screens 2) metrics were grouped together their meaning and dependences and colors were assigned for each group. This was done in initial designs we received, we only improved the colors a little. We do think that coloring groups of metrics help a user to bind them together. 3) probably we can give a user ability to change metrics color as they want, still we need to have some initial coloring for those who just launched an app. 4) about decreasing number of metrics on Dashboard --> this can be easily managed from Manage Dashboard screen, as well as re-arranged in order with drag&drop. Our team believe that this additional screen allow user to manage his Dashboard as he wants. But the useful thing can be - show Tutorials of using dashboard management at the first launch. What do you think?

twoolf commented 8 years ago

I think that I see the problem more clearly -- right now the Balance screen takes the first seven rows from the Comparison screen (Weight, BMI, Dietary Energy, Heart Rate, Step Count, Active Energy and Resting Energy). The problem is that this doesn't use seven different colors and also that it means several items are essentially overlapping. That's why we'd put them into different groups to begin with. So, if we do want to keep the color scheme informational, we should make sure that the Balance screen is restricted to seven items each of a different color. If we want the user to sort the rows and then to know that the first seven will be those on the Balance screen, we should find a way to mark that on the first screen, so that they realize what information is being selected from the first screen and then reflected again on the 2nd screen in a different format.

Also, on my build the 'manage dashboard has only checkmarks rather than drag and drop to rearrange. I like the idea of a drag and drop -- is that already implemented and thus something wrong with the build that I'm on?

twoolf commented 8 years ago

Adding on to this, when I use the check-boxes to remove items to display, it works on the first dashboard, but not the 2nd, so, e.g. moving from 21 to 11, I do see 11 items on the first screen, but the same seven on the 2nd (Balance) screen.

twoolf commented 8 years ago

adding again to this -- manage on first screen vs manage on 2nd screen are not linked -- I hadn't realized that they didn't go to the same place -- so right now, to adjust the seven on the 2nd screen its manage for that screen -- the default seems to be the seven rows (selected or not) in the 1st screen -- we should make this more user friendly --