A eulogy for Dark Sky, a data visualization masterpiece (2023)

Original Article ↗ Hacker News Discussion ↗

Dark Sky, the once-beloved hyperlocal weather app known for its elegant, information-dense visualizations and eerily accurate “rain in X minutes” alerts, is widely mourned after its shutdown following Apple’s acquisition. Commenters argue that while Apple’s Weather app has absorbed many of Dark Sky’s features on paper, it falls short in clarity, reliability, and historical data, prompting users to seek out replacements like Carrot, Merry Sky, Weather Strip, and various APIs and government data sources. The exchange highlights a broader frustration with large tech acquisitions that dilute niche, high-quality tools and a strong interest in better weather data design, including metrics like dew point, cloud cover, and past-weather context.

Dark Sky’s Strengths and Unique Features

  • Widely remembered as uniquely clear, information‑dense, and visually concise.
  • Minute‑level rain alerts (“rain starting in X minutes”) were seen as freakishly accurate and practically useful (biking, motorcycling, outdoor planning).
  • Dynamic main screen that changed based on situation (adding radar, combined precip/temperature, etc.).
  • Rich history view: users could inspect weather for specific past dates and see past days alongside forecasts for context.
  • Extra controls: configurable notifications (thresholds for precipitation chance/temperature), dew point and humidity visualizations, hourly cloud cover, and “cool storms” radar highlights.

Comparison with Apple Weather

  • Some argue current Apple Weather has feature parity: radar, precipitation graphs, notifications, user reports, etc.
  • Many others find it cluttered, slow, and less legible; they see Dark Sky’s information design as a “missing feature” in itself.
  • Complaints include radar tiles that don’t load, inconsistent data between devices, limited history (only ~1 day back), and harder access to detailed metrics (dew point, “feels like,” cloud cover).
  • A minority report Apple Weather as accurate and minute‑precise in their region; others call it “hot garbage.”

Accuracy and Hyperlocal Forecasting

  • Strong nostalgia for Dark Sky’s hyperlocal rain timing; some say Apple’s inherited alerts are now “comically inaccurate.”
  • Others recall Dark Sky degrading even before the acquisition, or never being especially accurate in some microclimate‑heavy areas.
  • Explanations discussed: radar coverage limits, reliance on NEXRAD, reduced aircraft weather data during COVID, possible funding issues for public data, and climate‑driven complexity.
  • Unclear whether Apple still uses Dark Sky’s original backend or significantly changed data sources/models.

Replicas, APIs, and Alternatives

  • Many replacements cited: Carrot (with Dark Sky‑like layouts), Merry Sky, briefsky, Weathergraph, Weather Strip, FlowX, MyRadar, Windy, Weather Underground, yr.no, MeteoSwiss, Breezy, Shadow Weather, national weather service graphs, and DIY dashboards.
  • Pirate Weather reimplements the Dark Sky API and powers several clones.
  • Some users value model‑explorer tools (e.g., viewing multiple forecast models side‑by‑side) over a single “smart” forecast.

Meteorology vs. Visualization

  • Meteorologists quoted elsewhere describe Dark Sky as essentially a radar‐extrapolation and graphics tool rather than a full physics‑based forecast system.
  • Some commenters see this as gatekeeping: simplistic nowcasting can still solve the “is it about to rain on me?” problem better than complex long‑range models.
  • Consensus: Dark Sky’s main innovation was not new physics but outstanding short‑term radar extrapolation plus superior visualization.

Broader Reflections (UX, Acquisitions, Business Model)

  • Frequent lament that large‑company acquisitions (Apple–Dark Sky, Google–Sparrow, Weather Company–Weather Underground) degrade once‑excellent niche apps.
  • Some blame Apple for “destroying” value; others point out the founders chose to sell and likely couldn’t sustain data/compute costs without subscriptions.
  • Debate over why no perfect clone exists: data costs, need for ongoing revenue, difficulty matching both nostalgia and UX polish.
  • Meta‑threads question why people care so deeply about weather detail and why, as engineers, they don’t simply build their own replacements.