Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decimal values should have fixed points #2920

Closed
anonymous-matomo-user opened this issue Feb 12, 2012 · 4 comments
Closed

Decimal values should have fixed points #2920

anonymous-matomo-user opened this issue Feb 12, 2012 · 4 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone

Comments

@anonymous-matomo-user
Copy link

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

@mattab
Copy link
Member

mattab commented Feb 12, 2012

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
Copy link
Author

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
Copy link
Member

mattab commented Feb 12, 2012

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.

@anonymous-matomo-user
Copy link
Author

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

@anonymous-matomo-user anonymous-matomo-user added this to the 1.7 Piwik 1.7 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

2 participants