@anonymous-matomo-user opened this Issue on February 12th 2012

Currently all the values with decimals (average actions per visit) have a floating decimal. I.e. they will display 4.2 or 5.8, but if they are an integer it will just show 4 or 5, whereas it should display 4.0 or 5.0 to be consistent.
Keywords: decimals, UI, user experience

@anonymous-matomo-user commented on February 12th 2012

Attachment: Obviously it's not a huge deal, but 90% of the time it's going to have a decimal, so when you're quickly scanning this widget it's easier to pick out a X.0 decimal number than have it get mixed back in with all the single digit values.
Untitled-1.png

@mattab commented on February 12th 2012 Member

Thanks for the suggestion, but I disagree here. It is best to show less information when the extra information does not add value. In particular, showing .0 will have users think more (and convert in your brain 5.0 to 5 which takes mental energy).

@anonymous-matomo-user commented on February 12th 2012

Replying to matt:

Thanks for the suggestion, but I disagree here. It is best to show less information when the extra information does not add value. In particular, showing .0 will have users think more (and convert in your brain 5.0 to 5 which takes mental energy).
Not so. When scanning the visitors overview widget, if you are looking for a particular value (the average actions per visit) your eye automatically looks for the value closest to what you think it should be. Personally I scan quickly for two digits. When it's only one digit, it gets jumbled up with the other values (especially the average visit duration value) and I have to spend mental energy figuring out which is the value I'm looking for. Then you have to read the full descriptions (minutes, downloads, ah there it is, actions). IMO, way more mental energy to scan for a floating decimal.

@mattab commented on February 12th 2012 Member

Can you please post a screenshot of this showing that it makes it harder?

Maybe we could show the fixed point where it makes sense, if indeed it helps.

This Issue was closed on February 12th 2012
Powered by GitHub Issue Mirror