Live data from Hacker News

WeatherKit

developer.apple.com

31–40 of 203 posts

Re: WeatherKit

#31
post #4

Earlier quoted context omitted.

Says there’s a REST API?

Oops, that's what I get for not reading closely enough! In my defense, my eyes glazed over after the fourth Apple-product-OS version number ;) but yes, my bad on that Looks like it's 500k calls per month per Apple Developer Program account, so essentially $99/yr. Not totally unreasonable pricing, although I wish I could buy it a la carte. It's a bit out of my price range for hobby projects. If I ever start developing…

OpenWeather is better and has 1M calls per month for free.

https://openweathermap.org/price

Re: WeatherKit

#32
post #31

Earlier quoted context omitted.

Oops, that's what I get for not reading closely enough! In my defense, my eyes glazed over after the fourth Apple-product-OS version number ;) but yes, my bad on that Looks like it's 500k calls per month per Apple Developer Program account, so essentially $99/yr. Not totally unreasonable pricing, although I wish I could buy it a la carte. It's a bit out of my price range for hobby projects. If I ever start developing…

OpenWeather is better and has 1M calls per month for free. https://openweathermap.org/price

Why is it better? I thought everyone agreed Dark Sky was the best one?

Re: WeatherKit

#33
post #19

I learned in a meeting at my last job that many weather apps solely exist to collect and sell location data. Don’t have specific evidence but it seemed to be par for the course. So I’m glad to see this API, hopefully it’ll help more privacy focused weather apps thrive.

Apple has continued to take on services third parties previously used to exploit the private information of Apple’s customers. This includes Apple Card, but also the recently introduced multi-week payment options Apple is offering to buy its products. (Previously offered by other services “for free.”) I have no doubt that Apple is looking at how data is leaking across the ecosystem and is seeking to stop it as much a…

What business advantage does it being to Apple to (just) stop those data leaks?

Re: WeatherKit

#34
post #33
post #19

Earlier quoted context omitted.

Apple has continued to take on services third parties previously used to exploit the private information of Apple’s customers. This includes Apple Card, but also the recently introduced multi-week payment options Apple is offering to buy its products. (Previously offered by other services “for free.”) I have no doubt that Apple is looking at how data is leaking across the ecosystem and is seeking to stop it as much a…

What business advantage does it being to Apple to (just) stop those data leaks?

It is possible they don't get 30% cuts of any of that sale of info so want it out to avoid contagion ("but they dont pay 30% on X" spreads to "I don't want to pay 30% on Y and maybe we'll go to court over it").

Based on the emails that have come out from various trials, they want a 30% cut of everything, eventually including real world services mediated through the phone.

Re: WeatherKit

#35
post #16

Does this provide any historical data like daily max, min temperatures? Quality historical weather data would be great to have in this.

I think the REST API is supposed to support this, but I didn't spot anything relevant in the Swift interface.

Re: WeatherKit

#36
post #17

Earlier quoted context omitted.

I was questioning why WeatherKit needs a "platform-specific Swift API" at all. If the general REST API in Swift is good then WeatherKit can be integrated into Swift apps as easily as any other service. If it's not easy then improvements to the general REST API could be considered.

My hunch, but I'm not sure about this, is that there might be some centralized caching going on on with the native SDK, so that if multiple apps use the WeatherKit API, they can share the cache.

No idea if there's caching across apps, but similar requests from the same app does hit a cache.

Re: WeatherKit

#37
post #17

Earlier quoted context omitted.

There is a rest api. > 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. [edited for tone]

I was questioning why WeatherKit needs a "platform-specific Swift API" at all. If the general REST API in Swift is good then WeatherKit can be integrated into Swift apps as easily as any other service. If it's not easy then improvements to the general REST API could be considered.

The Swift API is ergonomic and strongly-typed.

Re: WeatherKit

#38
post #31

Earlier quoted context omitted.

Oops, that's what I get for not reading closely enough! In my defense, my eyes glazed over after the fourth Apple-product-OS version number ;) but yes, my bad on that Looks like it's 500k calls per month per Apple Developer Program account, so essentially $99/yr. Not totally unreasonable pricing, although I wish I could buy it a la carte. It's a bit out of my price range for hobby projects. If I ever start developing…

OpenWeather is better and has 1M calls per month for free. https://openweathermap.org/price

Those 1M calls per month do come with a pretty onerous 1 call/second limit.

That limits the number of use cases quite dramatically.

Re: WeatherKit

#39
post #25
post #17

Earlier quoted context omitted.

I was questioning why WeatherKit needs a "platform-specific Swift API" at all. If the general REST API in Swift is good then WeatherKit can be integrated into Swift apps as easily as any other service. If it's not easy then improvements to the general REST API could be considered.

> I was questioning why WeatherKit needs a "platform-specific Swift API" at all So you can use it without having to deal with the low level detail of HTTP connections.

Low level detail of HTTP connections is already abstracted away in any general REST API.
Post reply on HN