https://weather-dj.netlify.app/
Let's hope that in the future Apple continues to deliver the same API structure as Dark Sky did, because it will be a big shame if they did some changes or limitations to it. Although I only use this app mostly for my personal use, the effort that I've put into this would be for nothing's worth.
And no, Apple is not interested in sharing its API's with anyone.
Funny how people will state ‘facts’ that match their internal perceptions, regardless of what’s been publicly stated over and over again.
Apple has released the WeatherKit API, which is privacy-first, and pretty much provides what Dark Sky did.
My "internal perceptions", as you called them, was based on Apple's history. Not any Apple hate. The fact that they are opening something up is very cool, I'm glad to hear it. But a single open API does not address an overall very closed ecosystem.
Edit: I was wrong. It has REST API and access from other platforms are allowed.
> It’s easy to use WeatherKit in your apps for iOS 16, iPadOS 16, macOS 13, tvOS 16, and watchOS 9 with a platform-specific Swift API, and on any other platform with a REST API. [0]
I know people who are already using it in random python scripts and whatnot, e.g. https://sixcolors.com/post/2022/06/adding-apple-weatherkit-d...
Dark Sky has been exceedingly clear about this for a very long time.
I don't know how the parent commenter missed it, unless they started the side project several years ago and never went back to check the API docs.
But today's announcement has nothing to do with discontinuing the Dark Sky API. They gave ample warning about that as well as replacement guidelines long ago.
Some suggestions:
- The hourly forecast icons are hard to tell apart. They're small, and blue raindrops blend in with the blue gradient behind the icon.
- The checkmark button on starred locations is hard to understand. It looks like it should confirm something (especially beside the red X), but it I guess maybe it selects the default location? The button could use alt text, too.
- The 7-day forecast feels busy. Maybe de-emphasize the date (lower font weight or smaller size for the calendar day, and maybe a shorter date format)
- The search box would benefit from suggesting places. Less to type (especially on mobile), and weather apps are inconsistent about what location queries they support and suggestions give confidence I'm using a new app correctly.
Apple recommends switching to WeatherKit's API. It is not free, requiring a paid Developer Program membership, which is $99/year.[1] That includes 500k API calls/mo.
On that linked WeatherKit page, they include a DarkSky migration guide. There are fields that are no longer being offered. (The fact that `temperatureHigh` doesn't have an analog makes me wonder if the table isn't telling the full story)
Edit: it’s not. See https://developer.apple.com/weatherkit/get-started/
Err, dark sky announced this well over a year ago, and was acquired 2 years ago - this is not news.
"Developers, Apple’s new WeatherKit API lets you incorporate Apple Weather forecast data into your app and is available for iOS, iPadOS, macOS, tvOS, and web."
Sorry for your loss :-/