Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yes I’ve worked at FAANG companies, and yes it’s great Instagram used AsyncDisplayKit (which is archived by the way).

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)



It‘s about as easy to do what you describe in react native without performance issues, but like others have mentioned there is more to this pattern related to scrolling content, snap points, interaction with the content behind it...


What performance issues? You’re telling me the native implementation has performance issues over RN?


It's a bit more difficult to make it natively than what you've described if you want to track the users gesture and deal with content that also scrolls.

Not more than a few days of work to get right at max but still a bit more.


Sure.

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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: