Using Android, I want to use ECMWF as it’s the best model. Unfortunately this doesn’t include cloud cover or humidity level which causes “no data” to show as a watermark on my graphs. I’d like to use ICON to source this missing data like weather.app does
@hallucynogenyc Hello and Welcome to the Forum and Thank You for Using Flowx
It’s on the todo list.
Thanks, do you have an ETA? I prefer the Flowx UI but “get each piece of forecasted data from best source available” is what the windy app does by default and I’m used to that ![]()
I don’t have a hard ETA. I’m currently rewriting the entire backend code as part of the port to Apple. It has been two+ years so far.
I’m hoping to release Apple in June. Then I plan to focus on getting this code to Android which I expect will take a few months. Then I’ll look at a “Source Set” editor - I don’t expect this will take long since most of the logic is there and I can currently create these manually.
Regarding the “best source available”, I don’t mixing weather data from different sources since it might deceive users. With the editor, the user can mix sources themselves and they will know what is mixed.
I don’t mix either I like being able to compare the individual sources being a weather geek it’s very interesting what each model is predicting and what local meteorologist predict to what actually happens. it’s always a mix of all is what makes weather so fun for me
Came here to suggest precisely this. None of the sources is particularly good on rain, but ECMWF seems more reasonable today in my area. But… no clouds, no gusts, no humidity… It’d be great if we could pick and choose sources for each. Might make the overall picture incoherent, but if it’s an option, it’s a feature, not a fault.
Makes sense to be a paid feature. It’d also dove in well with that suggestion I made to you a while back of charging per premium data source rather than maintaining 2 versions of the same app (for each OS!).
Still, mixing data from different sources is a bad idea both in terms of 1. the potential confusion it might cause and 2. the amount of code and UI extras that will be needed. The amount work due to support and code maintenance it will create will not justify the feature, especially when you can just change data sources to view the different data and also ECMWF has released more models for free that has cloud.
Great! Will you include them?
Of course. I work on Flowx pretty much every day.
My plan when I started Flowx (WeatherBomb) in 2012 was to spend 6 months to finish the Android version and then 6 month writing an iOS version. Over ten years later, I released the iOS version.
Developing an app and support users is not as easy as you think.