60fps and gesture handling is a breeze on iOS. There is nothing impressive about achieving this. We’ve had it for 13 years now on iPhones. We now have 120hz displays on iPads, and guess what, animations there are easy to achieve too, at 120fps.
https://www.youtube.com/watch?v=8ngXakpE2x8
I guess you probably have better insight than the devs of two of the most popular native apps, though. Cheers!
For most companies (maybe all), it’s not needed. Apple is doing a fantastic job abstracting views into SwiftUI and Android team is doing the same with Jetpack Compose.
Then what? More abstractions over abstractions to achieve 60 or 120 FPS through another framework?
And this is not related to the OP post, making these bottom sheets is a breeze. Literally:
1.) Custom ViewController with custom UIView as base view 2.) Add as child or present over root controller 3.) Translate and animate custom base view from bottom (top... left... whatever the hell you like)
Not more than a few days of work to get right at max but still a bit more.
4.) Put scrollview inside base view 5.) Register pan gesture and delegates and write logic for full, mid, none snap points
You clearly don’t need another whole framework to do the above
Unneeded abstractions
They developed it to address developer performance and ensure consistency.
Apple's layout APIs certainly could be a lot better but this framework only seems necessary if you want to avoid having the same teachable moments over and over for thousands of junior engineers.