Health, home and travel decision
EverythingWeather
A competent developer can implement a useful subset (local forecasts, radar tiles, favorites, push alerts) using open APIs and open-source tooling, but reproducing the full commercial app (high-res/pro data, polish, watch/CarPlay support, robustness) requires ongoing third-party data costs and more engineering.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off76 h to build
$50/mo6 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All EverythingWeather alternatives, with the arithmetic →
What a replacement has to do
- Fetch forecast and observation data from NOAA/NWS (and a fallback API), render localized hourly/daily forecasts and radar layers, allow saving/reordering favorite locations, and send push alert notifications for watches/warnings and user threshold alerts.
What it still won’t have
- Polish and UX refinements of the commercial app (widgets, Apple Watch/CarPlay)
- Pro-only high-resolution satellite/radar products and historical climate hub
- Built-in fallback strategies and robustness for NWS outages
- Ongoing customer support and bug triage from the app author
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
EverythingWeather does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal cross-platform mobile weather app using Expo React Native, a small Node/Express backend (host on Vercel/Render) and a hosted Postgres (Supabase) for favorites. Core features in scope: (1) Fetch NOAA/NWS forecast and observation endpoints plus an open fallback API (use open-meteo) and normalize responses; (2) Localized hourly and 7-day forecast screens with simple charts; (3) Map view showing radar/satellite tiles via WMS or tile server with ability to toggle basic overlays (radar, watches/warnings); (4) Persist favorites and user settings; (5) Push notifications for NWS alerts and user threshold alerts using Firebase Cloud Messaging (FCM) and APNs; (6) Basic authless onboarding, privacy-compliant analytics (opt-in). Out of scope: advanced PRO-only satellite products, Apple Watch/CarPlay widgets, extensive climate hub, commercial licensing of third-party premium data. Include error handling for network and API outages, unit tests for API integration and core UI flows, and deployment scripts for Expo and the Node backend.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productEverythingWeather homepage — Data Straight from NOAA's National Weather Service
- official productEverythingWeather homepage — EverythingWeather Pro features
- official productEverythingWeather homepage — feature list (radar, observations, notifications)
- open sourcebreezy-weather/breezy-weather
- open sourcePranshulGG/WeatherMaster
Integrity checks
What held up, and what did not.
