Good to know. But I must admit that I expected Apple at least to allow that you can have privacy for you and your code.

Good point. I’m afraid you have to sign in if you what to use more tokens than you get with the free version provided through Apple 😞

Until now I didn’t see any horror stories from the first beta. Wirst things are there the new UI doesn’t work in all places very well ¯\_(ツ)_/¯

Not until now, but I only took my main media consumption iPad 😉

But what about the nice snapping cursor they had before? That was one of the best features on iPad.

Sounded like “Swift Assist” is more like “We put ChatGPT in Xcode”. I hope I’m wrong.

I know your pain. I’m currently fighting some Swift Data migrations, but also got some working in the past 😅

I can nearly see your intention in this image 😉

I didn’t find a reason to use them yet ¯\_(ツ)_/¯

Have fun 😉

Right, that’s what I meant. I think to remember that the „original“ cover flows used perspective distortion to create the stacked effect and prevent this flipping

Nice one. I’m currently implementing a theme feature, too. I would spread the tiles more on the y axis to avoid this jumping when switching the top most tile to the next one. It would also allow the users to catch more themes with the eye at a time.

If it is about a url, you may try to work with Etags (if the server supports it). You need to store the Etag from the first response and pass it to the next request. The server should return status code 302 (or 304, not sure at the moment) when noting changed or 200 with content when changed.