You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #1 I see that you were looking for some feedback on the previous (and current) design.
One thing that I find a bit clunky with the current design is the modal aspect of it, where you have to switch between the main "Weekly forecast" view and the individual day view (with combobox-like switcher between days).
This is a long shot, but have you considered an interactive stacked charts approach as a way to unify all of this into a single UI?
A bit like what you'd find on the "10 days" forecast here for example:
I don't know if you'd find this approach worthwhile for this application, I'm just throwing the idea out here. This is the same kind of idea that I'm suggesting in amit9838/mousam#130.
The text was updated successfully, but these errors were encountered:
So, in the last week I tried to add something like this with everything stacked into a single ui, but I always find it a bit to crammed and I want to keep a very simple ui design. I will try to add multiple graphs for temperature, wind and precipitations but as I said before I will implement it only if I find a way to keep a simple design with not to many informations in the same place. I really appreciate your suggestions, thanks! Also, I will keep this open to keep you updated if I figure out a way.
In #1 I see that you were looking for some feedback on the previous (and current) design.
One thing that I find a bit clunky with the current design is the modal aspect of it, where you have to switch between the main "Weekly forecast" view and the individual day view (with combobox-like switcher between days).
This is a long shot, but have you considered an interactive stacked charts approach as a way to unify all of this into a single UI?
A bit like what you'd find on the "10 days" forecast here for example:
I don't know if you'd find this approach worthwhile for this application, I'm just throwing the idea out here. This is the same kind of idea that I'm suggesting in amit9838/mousam#130.
The text was updated successfully, but these errors were encountered: