Christian SeligFeb 17, 2023

Reading about @dimillian's issues with SwiftUI and scroll performance in his Ice Cubes app compared to UIKit, and if I were Apple I'd be flying him down to profile his app and see where SwiftUI could be optimized more/what's going on.

Such a great app and showcase of SwiftUI, and even though complex, media-rich timelines with lots of elements can be complex to get right in UIKit, I think instilling community/developer confidence that "Yeah, SwiftUI can do this too" is really important.

Show threadJoe Barbere

@christianselig @dimillian not sure if this is applicable but there was a recent hackernews post regarding SwiftUI and infinite scrolling.

https://blog.timing.is/swiftui-production-experience-problems-solutions-performance-tips/

https://news.ycombinator.com/item?id=34556370

30,000 lines of SwiftUI in production later: We love it but you know there was going to be a “but”

timing.is shipped this month on the App Store. It was built entirely in SwiftUI. It was in development for 12 months. It would have been less if SwiftUI just gave. Unfortunately, repeatedly it would take.

_blog
Feb 17, 2023 at 6:35pmWeb
Show threadChristian SeligFeb 17, 2023
@joebarbere @dimillian Helpful but quite different I think, that seems to be about jumping through oodles of "cells" in a short period, where Thomas' seems to be more about the richness/complexity of individual cells (versus the app in this post) and scrolling slowly when not even scrolling that fast necessarily