Nesting UICollectionViews vs UIPageViewController

Question

I needed to implement the following: scrolling pages and displaying a tableview or collectionview with data relevant only to this particular page at the bottom of the screen. First, I tried using nested UICollectionViews, making the cell of the external UICollectionView equal to the size of the screen and setting the internal delegate of the UICollectionView to the containing cell (external cell of the UICollectionView). I ran into the problem that data is not loading properly in the internal view of the collection. The problem is better described in this question: nested UICollectionViews problem

Anyway, I looked more at the UIPageViewController as a possible solution to the problem. I have never implemented a UIPageViewController before and am not sure if this could be a good fit for my problem. If someone has done something similar before, please direct me to the right place or resource.

I would still like to go with nested UICollectionViews, if possible, and I don't quite understand why it works as desired. Once again, my problem is described better in the link above. Please report all options.

Answer 1

When using the UIPageViewController you must implement the reuse mechanism yourself, this is the only drawback that I see. Basically, I would prefer the UIPageViewController to call it cleaner than nested collections.