@jacobx@seanallen_dev In your investigation did you consider Pkl at all? If you did, Iโd be curious to know what drawbacks may have been for it. Given its origin I thought it would have been a good choice.
Fun fact: the creator of CoreAnimation is one of the creators of SwiftUI!
The decision to run animations in the app process rather than the render server (as CoreAnimation does) was one of the earliest and most fundamental decisions we made when designing SwiftUI.
Some of the most distinctive experiences of using an iPhone, like UIScrollView rubber banding and SpringBoard app switching are only possible as client-side animations.
But these experiences arenโt easy to build with UIKit!
This is because if you want a UI to be fully interactive and interruptible by the user while itโs animating, it has to be running in the same process as the event handling.
In fact, in iOS 18 we added new APIs to AppKit and UIKit to adopt the SwiftUI client-side animation model.
There are a lot of valid critiques of SwiftUI. The fact that SwiftUI doesnโt use CoreAnimation for its animations is not one of them.
@DonnyWals If you do any cross-training in preparation for you race and need a companion app ๐. https://t.co/iY1S1x9hBA
Or you could join via TF (I have some Apple Watch integrations hopefully releasing by next Monday)
@twannl Awesome ๐๐ป. I love the purpose of Instruments. But I find the experience overly cumbersome for what could be two tightly integrated products (Xcode / Instruments). Also the icon since Xcode 26 is ๐คฆ๐ผโโ๏ธ
From a construction site to a $70M empire, selling pillows.
@CreedMcKinnon arrived at @thatpillowguy โs Florida mansion at 5am, heโll never forget what came next.
Full video OUT NOW on our Youtube๐