2

I have worked with both UICollectionView and UITableView and its trivial to make UICollectionView look like table. What is more usage patterns are very similar, you don't have to learn a lot of new stuff to use it.

The question is are there any arguments for using UITableView and not UICollectionView? Or we can just switch to UICollectionView and forget about UITableView?

Rafał Sroka
  • 39,540
  • 23
  • 113
  • 143
Jaroslav
  • 1,389
  • 14
  • 27
  • 2
    CollectionView doesn't have a tableHeaderView and tableFooterView properties, which makes adding search bar functionality a pretty tough task – Eugene Mar 06 '14 at 13:50
  • 3
    There also edit mode and swipe to delete you get with UITableView that you'd otherwise have to implement yourself. – Mike Pollard Mar 06 '14 at 13:54

1 Answers1

4

I don't think so.

For example, if you want to have some stickies header, you've got to create a custom Layout for your UICollectionView, whereas, it's really easy with UITableView.

Moreover you have plain and grouptableViews, which is really usefull.

In my own opinion, I would say sometimes it's better to mutualize and use a collectionView (if it's a tableview on iPhone and a collectionView on iPad for instance), but not everytime.

eonil
  • 83,476
  • 81
  • 317
  • 516
Rémy Virin
  • 3,379
  • 23
  • 42