13 articles on Scroll Performance for iOS performance
Showing 13 of 13 articles (Page 1 of 1)
Jacob Bartlett puts SwiftUI and UIKit through the ultimate stress test: a feed of 22,000 animated GIFs running at 120fps. The results might surprise you.
Jacob Bartlett from Jacob's Tech Tavern puts SwiftUI scroll performance under the microscope. Can it really hit 120fps with complex infinite feeds, or does the magic come at too high a cost?
Bevan Christian from IDN Engineering tackles a problem every iOS dev knows: that janky scroll when images load in UITableView. His solution? iOS's built-in prefetching API that most developers overlook.
Swiggy's Android team was hitting scroll performance walls with traditional RecyclerViews. Their solution? Facebook's Litho framework, which delivered massive performance gains.
Zoltan Lippai from DoorDash cracked a problem that stumped early SwiftUI adopters: how do you programmatically scroll when Apple didn't give you the tools? His team built their own solution for iOS 13.
Tokopedia's iOS team was crashing on UICollectionView batch updates. Their solution? Build a better abstraction inspired by Instagram and SwiftUI.
Phong Lam from Walmart Global Tech tackles a problem every mobile dev faces: infinite scroll that doesn't tank performance. His solution? Stop rendering everything and start being strategic.
Monzo's iOS app got 60% slower over time, and their team structure was partly to blame. Here's how they fixed it and prevented it from happening again.
Zalando's engineering team faced a tricky challenge: how do you know if a user actually *saw* an item in a scrolling list, not just flew past it?
React Native just killed ListView. The new list components solve memory leaks, stale rows, and ignored bugs that plagued mobile developers for years.
Twitch was dropping frames like crazy. Chat messages were taking 200ms to render when they had just 16.667ms to work with for smooth 60fps video.
Zalando's iOS team challenges a widely-cited performance myth about UITableView that's been misleading developers for years.
Dropbox engineers faced a brutal reality: reading 5,000 photos from SQLite took a full second on a Nexus 5. For users with 100,000+ photos, the standard approach would be unusable.