When to use UICollectionView instead of UITableView?

Question

I found that UICollectionView is like an upgraded version of UITableView introduced in iOS6, but when should I choose UICollectionView

Answer 1

Its totally dependent on how your data to be shown. As mentioned by many above, if you require only single set of data and that too not complex, go for UITableView else use UICollectionView.

UICollectionView is customization friendly.

If you are dealing with multiple cell heights or so, then go for UICollectionView.

Answer 2

Both are depends on the requirements. Table Views also have support for a variety of editing scenarios. This support has not been implemented in the Collection View classes. If you are converting from a Table View that relies on these methods, expect to do a little extra heavy lifting in the Collection View. Collection View section headers can be placed anywhere within the view. and UITableView don't need to set buttons with tags or other things by getting selected items values.

Answer 3

Although it's not required, I always use a collectionview. That way I can easily adapt how my collections are presented for differing resolutions. A plus is that it's ready to quickly add new types of cells when refactoring in the future.

I see no point of tableviews. It's very simple to use a collection view to represent a table. IMO.