Perhaps the wind vector icon was designed for phones with lower screen resolution?
Modern phones has so high resolution that the icon becomes verry small, and it is hard to detect the direction of the tiny arrow, or even that is actually is an arrow.
I suggest an update of the icon to a more simple design, so that the direktion of the arrow is more clear, eaven when it is presented by the tiny pixels on a hi-resolution phone screen.
It’s not clear to me that this icon is a prevalent problem among all users so I don’t really want to spend half a day designing a new icon, adding it to the app, releasing it and getting a backlash for the change.
I hope you understand my position. It’s not that I don’t want to change it for something better. It’s just not clear a new design is better and it’s not clear this is a good use of my limited time.
For example, I’m currently working fixing the broken RTOFS which is not showing up in the right position on the map. Should I be working on this new icon or fixing RTOFS or other things like adding other data like UV to the graphs, or an editor to choose what the fallback data sources should be.
It’s just hard to justify working on this.
My suggestion is that you design an icon, post it here and see if you can get enough support to test it out. If you get enough support and it makes sense, I’m happy to release it in beta and ask for feedback.
BTW, the original design some 7+ years ago was just an arrow.
The problem with an arrow is whether the arrow is indicating the direction the wind is coming from or the direction the winds is going?
The current design is to capture this dual concept of the direction the wind is coming from (position in the circle) and the direction the wind is going (the direction of the arrow). And the dot in the middle is you.
In my opinion the actual icon is practical to indicate from where the wind comes, which is the only system i know and have ever seen to indicate wind directions, and it is nice and pretty.
Dont see any reason to change that.
More important , i think, is to solve the 180° bug with DWD data source