I posted the exact same thing in rbtc , it was downvoted to oblivion within a minute . <| sep |> He looked like he did when he was in his first season with Dortmund Lacked confidence to finish . But his third season he was on fire . ManU fans might have to wait another season before Mkhitaryan finds his stride again . <| sep |> DARIUS SLAY CAN FUCK MY BITCH <| sep |> Well as long as it is less than lets say 500 cells collection view should be ok . After that or maybe after 1000 , initialisation of layout will definitely be slow and you would have to implement some lazy loading logic . I have done so for my current project 8 where i used to have a data source of around 2 k 2 images and 2 collection views in the same screen . If i try to load all the data on the collection view i would have to wait for about 2 seconds before the collection view was actually rendered and the app was like frozen during that time . So what i did was a memory pagination where i was lazily loading and removing data into the CollectionView as the user was scrolling . Fortunately the way it reloads data is so fast that the user wont even understand it , as long as its not scrolling . It is now working pretty well . Imho collectionView is the way to go nowadays , unless its a dummy list . , provided the flexibility you get via the layout class and all the cool animations you can do if you know its api .