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.

▲

imiric 3 hours ago | parent [-]

> 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.

	▲	JumpCrisscross 3 hours ago \| parent \| next [-]
		> 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.
	▲	plantain 2 hours ago \| parent \| prev [-]
		Good luck getting ECMWF ensemble data for free.