{"id":28624,"date":"2020-04-10T14:16:45","date_gmt":"2020-04-10T18:16:45","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28624"},"modified":"2020-04-10T14:17:33","modified_gmt":"2020-04-10T18:17:33","slug":"cloudkit-impressions-from-a-netnewswire-developer","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/04\/10\/cloudkit-impressions-from-a-netnewswire-developer\/","title":{"rendered":"CloudKit Impressions From a NetNewsWire Developer"},"content":{"rendered":"

Maurice Parker<\/a> (tweet<\/a>):<\/p>\n

One area that CloudKit outshines our RESTful service implementations is that it gets notifications when the data changes. This keeps our data more up to date. In the RESTful services, we sync which feeds you are subscribed to every so often via polling. This happens at shortest around every 15 minutes. Realtime updates to your subscription information isn’t necessary, but it is fun to add a feed on your phone and watch it appear in realtime on the desktop.<\/p>\n

[…]<\/p>\n

One thing I wanted to do was provide a centralized repository that knew which feeds had been updated and when. I planned to have a system that would use the various NetNewsWire clients to update this data and notify the clients. My theory was that checking one site for updated feeds would be faster than testing all the sites to see if their feeds had updated.<\/p>\n

I ended up giving up on this task. I think it would have been possible to implement in CloudKit, but would not have been faster than checking all the sites for their feed updates. […] There is no such thing as a “JOIN” between CloudKit records. If I could have connected data from more than one record per query I could have done some data driven logic.<\/p><\/blockquote>\n\n

I’d like to switch (back) to NetNewsWire when this ships, although I haven’t decided what I’ll do about the smart folder and Pocket features I use in ReadKit.<\/p>\n\n

Previously:<\/p>\n