Your phone comes with a free weather app. There are thousands more free apps for folks who don’t mind ads.
Weather requires ongoing costs. It’s always going to need to be maintained because meteorological models are evolving. Anything beyond a viewport will need to track and metabolize those changes.
I strongly doubt that this company runs their own weather stations or meteorological models. Their only recurring cost is API access to the companies that provide weather data, a negligible amount of IT infrastructure, and their employees. Considering that there are many free weather APIs, and that a polished frontend can be built by a single person, what exactly are the overheads?
To be fair, I'm not criticizing the subscription model. I think it makes sense for software that needs to be continually maintained. But a weather app shouldn't have large maintenance costs that couldn't be covered by a one-time payment. A big reason why companies love the Apple ecosystem is because subscriptions have been normalized, and users are used to paying them regardless if the model actually makes sense for the type of software.
> strongly doubt that this company runs their own weather stations or meteorological models. Their only recurring cost is API access to the companies that provide weather data
No. But I'd suspect a tabula rasa approach to weather–particularly given it hasn't been rolled out globally in one go–incorporates satellite data, local measurements, et cetera.
Again, that may not take constant subscriprtion. But it does take constant expert monitoring and awareness.
> Considering that there are many free weather APIs
If you're a glorified viewport into these APIs' data, you may be able to stick with their most-static data and fire and forget. In reality, what those outputs mean change as the models and techniques evolve. There are new APIs with new data constantly coming out, and they're often adding connectors.
> a weather app shouldn't have large maintenance costs that couldn't be covered by a one-time payment
The only way I see this working is if the user is explicitly aware the app can break at any time if one of the APIs change anything, which they often do, and that this may not cause any obvious failures, just a decay in the app's accuracy or usefulness.
> No. But I'd suspect a tabula rasa approach to weather–particularly given it hasn't been rolled out globally in one go–incorporates satellite data, local measurements, et cetera.
There most likely won't ever be such an effort - even in companies that are targeting verticalization of the "weather supply chain" (proprietary observations + models + decision support tools) - if only because it would be utterly foolish to exclude the vast amounts of data collected by government agencies and the wide variety of players in the weather enterprise. At best, verticalized weather companies can produce niche value over baseline from the single modality of proprietary data they collect.
The infrastructure for observing and forecasting the weather is incredibly sophisticated, and has been evolving for about 150 years at this point. The quality of contemporary numerical weather prediction likely doesn't leave much headroom towards the threshold of fundamental physical limitations on predictability. This is why there are groans and eye rolls from the weather community each time a new player steps forward with yet-another-AI-model-trained-on-ERA5-reanalysis and boasts some comically small improvement in average forecast skill.
With all that being said, there's likely an exciting frontier opening up as the AI models push towards encompassing data assimilation. But the applications that start to become extremely interesting there won't have any noticeable impact on average forecast quality for your typical weather app.
I only have one Apple devices (an iPad) but from what I seen the subscription is popular on it. I wanted to use Infuse, a video player, for my Jellyfin server but the lifetime price was $100 or a $2/month subscription. Also was interested in Panels, a comic book reader, for my Komga server. Panels was more reasonably priced ($20 for all updates to the current major version) but it also a subscription tier at $1.5/month.
How do you expect them to pay for their costs and service fees? One time payments of $1-$10 don't cut it. People aren't paying massive one time fees for mobile apps
Your phone comes with a free weather app. There are thousands more free apps for folks who don’t mind ads.
Weather requires ongoing costs. It’s always going to need to be maintained because meteorological models are evolving. Anything beyond a viewport will need to track and metabolize those changes.
> Weather requires ongoing costs.
I strongly doubt that this company runs their own weather stations or meteorological models. Their only recurring cost is API access to the companies that provide weather data, a negligible amount of IT infrastructure, and their employees. Considering that there are many free weather APIs, and that a polished frontend can be built by a single person, what exactly are the overheads?
To be fair, I'm not criticizing the subscription model. I think it makes sense for software that needs to be continually maintained. But a weather app shouldn't have large maintenance costs that couldn't be covered by a one-time payment. A big reason why companies love the Apple ecosystem is because subscriptions have been normalized, and users are used to paying them regardless if the model actually makes sense for the type of software.
> strongly doubt that this company runs their own weather stations or meteorological models. Their only recurring cost is API access to the companies that provide weather data
No. But I'd suspect a tabula rasa approach to weather–particularly given it hasn't been rolled out globally in one go–incorporates satellite data, local measurements, et cetera.
Again, that may not take constant subscriprtion. But it does take constant expert monitoring and awareness.
> Considering that there are many free weather APIs
If you're a glorified viewport into these APIs' data, you may be able to stick with their most-static data and fire and forget. In reality, what those outputs mean change as the models and techniques evolve. There are new APIs with new data constantly coming out, and they're often adding connectors.
> a weather app shouldn't have large maintenance costs that couldn't be covered by a one-time payment
The only way I see this working is if the user is explicitly aware the app can break at any time if one of the APIs change anything, which they often do, and that this may not cause any obvious failures, just a decay in the app's accuracy or usefulness.
> No. But I'd suspect a tabula rasa approach to weather–particularly given it hasn't been rolled out globally in one go–incorporates satellite data, local measurements, et cetera.
There most likely won't ever be such an effort - even in companies that are targeting verticalization of the "weather supply chain" (proprietary observations + models + decision support tools) - if only because it would be utterly foolish to exclude the vast amounts of data collected by government agencies and the wide variety of players in the weather enterprise. At best, verticalized weather companies can produce niche value over baseline from the single modality of proprietary data they collect.
The infrastructure for observing and forecasting the weather is incredibly sophisticated, and has been evolving for about 150 years at this point. The quality of contemporary numerical weather prediction likely doesn't leave much headroom towards the threshold of fundamental physical limitations on predictability. This is why there are groans and eye rolls from the weather community each time a new player steps forward with yet-another-AI-model-trained-on-ERA5-reanalysis and boasts some comically small improvement in average forecast skill.
With all that being said, there's likely an exciting frontier opening up as the AI models push towards encompassing data assimilation. But the applications that start to become extremely interesting there won't have any noticeable impact on average forecast quality for your typical weather app.
Good luck getting ECMWF ensemble data for free.
I only have one Apple devices (an iPad) but from what I seen the subscription is popular on it. I wanted to use Infuse, a video player, for my Jellyfin server but the lifetime price was $100 or a $2/month subscription. Also was interested in Panels, a comic book reader, for my Komga server. Panels was more reasonably priced ($20 for all updates to the current major version) but it also a subscription tier at $1.5/month.
How do you expect them to pay for their costs and service fees? One time payments of $1-$10 don't cut it. People aren't paying massive one time fees for mobile apps
The internet and software always costs someone.