What's so special about this weather app? I bet it draws data from the exact same monitors as other weather apps
Unlike most other weather apps, they developed a fairly sophisticated back-end system, that takes in data from a bunch of sources and combines it together.
And they have an API (the Dark Sky API) that offers a RESTful HTTPS interface to the data - it's very easy to make a query by sending it a specially constructed URL and get back well-structured JSON that gives all sorts of useful weather and forecast data for the specified location.
Turns out a lot of other weather apps were written that make use of this API, because it makes things terribly easy - you put all your effort into writing the pretty "front end" of the app, for displaying data, and make one call to their web server (periodically), to get all the data to display.
They also have a very nice front-end app ("Dark Sky" on the App Store, up until, today, apparently), that displays the information in a nice format. One of its highlights, though, is it's very good at working out rain, in a form like, "possible light rain, starting in 5 minutes, and ending 20 minutes later" - and you can have the Dark Sky app send this information as push notifications. It can be quite useful to find out it's likely to start raining half an hour from now, or whatever.
I have a home weather station I constructed that taps into the Dark Sky API for forecast information for my location - it queries Dark Sky's webserver every five minutes to get updated forecast information (and has been, 24/7, since 2016). I expected that I was going to have to switch to some competing service; there are a few such services - some charge, while some don't, if you make fewer than X queries a day/month/etc. (Dark Sky has always had a "free tier" like this), but this was going to involve adapting my software to an almost certainly considerably different data stream (fields that simply differ in name are not difficult to handle, but fields that work differently cause more of a headache - for instance, Dark Sky will send an array of structures describing the likelihood and intensity of rain for each minute for the next hour, while some other service may present similar information in an entirely different format, say, a number for how many minutes until the next time it might rain).
Upon hearing that Apple would have a WeatherKit API, I'd even considered the possibility of having a Mac mini running a Swift program (something I'd write) that reads data from WeatherKit and uses it to construct JSON data similar to the Dark Sky data, to feed into my system, rather than hacking up the system to use a different service. I'd been putting off a decision on this for a while.
But! But, I found out a little while back that Apple is
more or less, just rebranding the existing Dark Sky web-based API (I'll have to register to get the proper keys to use it, but that's quite straightforward). But it's basically the same data in nearly the same format, but will now be coming from an Apple webserver rather than from the Dark Sky webserver. I'll be able to adapt my system to use it in perhaps a weekend. It's funny how closely they copied the ruleset for using the API, too - I actually have, on my weather station's main screen (a Raspberry Pi 7" touchscreen display, which has been running in my living room near continuously since 2016), a tiny graphic in the corner that has a logo and says, "Powered by Dark Sky", which is one of the conditions required for using their data (the logo/text, in one of several different formats, needs to appear in your app, like in a help screen - since my weather station only has one display, it's on the main display). Switching to WeatherKit, I'm going to end up replacing that graphic with one that says something like, "Powered by 🍎Weather". Personally, I'll find it amusing to have an Apple logo on the screen of my own weather station.
So, to answer your second question, "I bet it draws data from the exact same monitors as other weather apps", well, yes and no - it uses a lot of sources that are available to other apps, but quite the opposite, it not only synthesizes the data from multiple sources together, but it also
provides that data to a lot of those other weather apps. And since Apple is supporting a web-based API, and not just, say, a Swift framework in iOS/macOS, a lot of other weather apps will still continue to use this data, and you could easily have, say, an Android app that uses the data, without any problem (they charge at various rates if you make over a certain number of API calls per day, but where Dark Sky's "free" tier was something like a couple thousand calls a day - intended use being for developing an app - WeatherKit's "free" tier covers, I think, half a million calls a day - sort of ends up being another really nice benefit of paying for an Apple Developer membership, along with programmatic access to iCloud storage space space for your app's shared data and such).
A lot of the good bits of the Dark Sky app have moved into Apple's updated Weather app that's included in iOS 16 (and soon to be in iPadOS). It's not the Dark Sky app of old, but neither is it the Apple Weather app of old. Best of both worlds? Not sure yet.
For what it's worth, this is a screenshot from my system, which has been running in my living room for six years (the righthand column is a touchscreen control for the living room's Hue lights with specific scenes, but these days I normally just ask Siri to set scenes):
