I’m confused why the daily minimum would include times outside the day. That doesn’t seem like a daily minimum by definition. The way Apple does it is exactly how I assumed it would work.
Is the alternative you described standard?
Is the alternative you described standard?
In almost all cases the coldest part of the day is right around dawn. That also happens to be the time of day when most of us are first leaving the house. That's a pretty important piece of information to have and it isn't there at a glance.
Probably true, and yet the counterexamples are when the temperature forecast is particularly important when I'm choosing what to wear. Any simplification of the temperature forecast into daily lows and highs will fail certain use cases, so I think it's very reasonable to make the daily lows and highs as well- and simply-defined as possible and provide an hourly forecast so that people can also check for the potential edge cases.
I don't see any defensible opinion to let the lows be during/before sunrise.
Can’t you just check Friday’s temps? I’m not sure why you’d expect this info out of Thursday.
Apple's weather app shows a low of ~40f.
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.