-
Notifications
You must be signed in to change notification settings - Fork 26
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
No units in temperature figures #5
Comments
I slightly prefer it like this. The app determines which units you use by your locale and you can choose the units in the settings. Anybody who doesn’t alternate between units or has a bit of common sense will know what units it’s in. Showing units is unnecessary and can be aesthetically unpleasant. |
"Common sense" is not so common as you would expect. |
Also, the number without units is just a number. No meaning at all. Units are important. |
Not showing temperature units is consistent with the Dark Sky interface: https://web.archive.org/web/20220707133449/darksky.net/forecast/40.7127,-74.0059/us12/en , which briefsky is modeled after. However, I can see the argument for showing it in at most one place, like the current temperature, so a user can quickly confirm they're using the right units. I'll leave this open for now in case others want to chime in. |
Perhaps a good compromise is to show the units on the upper right corner. This way there's some hint for the user somewhere. This is what Darksky interface did too. |
In that example, it seems the configuration form may have indicated which units were being used: For my app, I chose to show the unit in a single place for the current temperature. Also Celsius needs an extra digit to maintain the same precision as Fahrenheit. So Fahrenheit readings are always whole numbers, Celsius readings have a decimal point by necessity. See how it looks: https://weather-sense.leftium.com (Click/tap any temperature to switch between °F/°C) |
The text was updated successfully, but these errors were encountered: