The daily low is the lowest temp of the day. It could very well be in the future. But it’s certainly not in the next day, and it’s not from a specific hour. If you want to see tomorrow mornings temps look at tomorrow’s hourly temps.
Do you expect the daily high to work the same? So maybe at 4pm it’s down from the daily high and now it shows today’s high is actually some temp around 3pm tomorrow?
I get what you’re saying but in no way is that a daily high. More like a next 24 hour high but even then, do you want that? That means if it’s 80F at 3pm today and 90F at 3pm tomorrow and it’s 3pm, then the high will be 90.
It’s much easier to just accurately categorize these by day/hour and let the user find what they care about instead of warping definitions to anticipate certain use cases.
How about we categorise it by the day/night cycles like we have since before we walked on 2 legs? Not some arbitrary time model we created that happens to divide the night cycle at midnight. Daytime max, overnight min.
absolutely the radio and local news television forecasts have always had daily high and low boundaries, not sure what is up with these people’s atypical mental models? They must not have listened to the news on the radio or on television growing up? Why should an app create a UI design pattern that goes against the majority of people’s mental models.
Then don’t look at past temps.
The daily low is the lowest temp of the day. It could very well be in the future. But it’s certainly not in the next day, and it’s not from a specific hour. If you want to see tomorrow mornings temps look at tomorrow’s hourly temps.
Do you expect the daily high to work the same? So maybe at 4pm it’s down from the daily high and now it shows today’s high is actually some temp around 3pm tomorrow?
I get what you’re saying but in no way is that a daily high. More like a next 24 hour high but even then, do you want that? That means if it’s 80F at 3pm today and 90F at 3pm tomorrow and it’s 3pm, then the high will be 90.
It’s much easier to just accurately categorize these by day/hour and let the user find what they care about instead of warping definitions to anticipate certain use cases.
How about we categorise it by the day/night cycles like we have since before we walked on 2 legs? Not some arbitrary time model we created that happens to divide the night cycle at midnight. Daytime max, overnight min.
absolutely the radio and local news television forecasts have always had daily high and low boundaries, not sure what is up with these people’s atypical mental models? They must not have listened to the news on the radio or on television growing up? Why should an app create a UI design pattern that goes against the majority of people’s mental models.