From the product review (iOS/PRODUCT_REVIEW_2026-07-01.md, finding #2). Highest-priority product gap.
There is no background alerting: no UNUserNotification, no BGTaskScheduler/BGAppRefresh, no push. NWS/WeatherKit alerts are fetched only when a user opens a city's detail view and scrolls to the alerts section. A "weather app with severe alerts" that can't warn you unless you happen to open it is not delivering the feature users think they're getting.
Needs: an alerting service/mechanism (under investigation). Options to evaluate:
- WeatherKit alert subscriptions / Apple Push for alerts.
BGAppRefreshTask polling NWS alerts/active for saved US cities + local notifications (best-effort, OS-throttled).- A server-side component that watches saved locations and pushes.
Honesty stopgap: until this ships, make in-app / App Store copy explicit that alerts are view-only (checked when you open a city), not push notifications.
Related: alert failure honesty (#1) is already fixed on code-review-fixes.
From the product review (
iOS/PRODUCT_REVIEW_2026-07-01.md, finding #2). Highest-priority product gap.There is no background alerting: no
UNUserNotification, noBGTaskScheduler/BGAppRefresh, no push. NWS/WeatherKit alerts are fetched only when a user opens a city's detail view and scrolls to the alerts section. A "weather app with severe alerts" that can't warn you unless you happen to open it is not delivering the feature users think they're getting.Needs: an alerting service/mechanism (under investigation). Options to evaluate:
BGAppRefreshTaskpolling NWSalerts/activefor saved US cities + local notifications (best-effort, OS-throttled).Honesty stopgap: until this ships, make in-app / App Store copy explicit that alerts are view-only (checked when you open a city), not push notifications.
Related: alert failure honesty (#1) is already fixed on
code-review-fixes.