iOS Swift UICollectionView With Horizontal Pagination

Hey, today I’m presenting you horizontal pagination in swift 5. The reference I have taken from one of my organisation’s library.

Nickelfox/PaginationUIManager

If you are new bee then please refer to following links first

1. https://developer.apple.com/documentation/uikit/uicollectionview
2. https://www.raywenderlich.com/9334-uicollectionview-tutorial-getting-started

Horizontal Pagination

Basic pagination works as you pulled to a threshold value. Beyond that, it will hit API and gives some array items back, that you will append to the main array. Pagination consist of 2 things refresh all and load more. Refresh all works when you need fresh content from the beginning and load more works when you need more data at the end. In context with horizontal pagination you will drag collection towards the right to refresh all and in case of load more, you will scroll to last content and drag towards left.

So moving ahead and let’s create a new project name HorizontalPaginationDemo.

Project Setup

1. Open default Main.Storyboard, there is default view controller in Interface Builder (IB), add UICollectionView with top, left, right and height to 0,0,0 and 200 respectively.
2. There is a default UICollectionViewCell present in the collection view. Extend it and add UILabel in the centre.
3. Create an IBOutlet of collection view in default ViewController Class and delegates methods for no. of rows and cell for row.

func setupCollectionView() {
    self.collectionView.delegate = self
    self.collectionView.dataSource = self
}

1. For horizontal or vertical pagination we need to specify in which direction collection view will scroll strictly. So for that set collection view property alwaysBounceHorizontal to true.

self.collectionView.alwaysBounceHorizontal = true

5. Add a subclass of UICollectionViewCell name HorizontalCollectionCell and set this as a subclass for the same in IB.

6. Add IBOutlet of the label in above collection cell’s subclass. Add below method. Updating the background colour will differentiate cells.

func update(index: Int) {
   self.titleLabel.text = "\(index) Value"
   self.backgroundColor = index % 2 == 0 ? .lightGray : .lightText
}

7. Coming back to view controller class, add an array variable with an integer type. Initialize the array with some dummy data. Update collections delegate methods as shown below.

var items = [1,2,3,4,5]
..
...
extension ViewController: UICollectionViewDelegate,
                          UICollectionViewDataSource {
func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int {
   return self.items.count
}
func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {
   let cell = collectionView.dequeueReusableCell(
      withReuseIdentifier: "HorizontalCollectionCell",
      for: indexPath
   ) as! HorizontalCollectionCell
   cell.update(index: indexPath.row)
   return cell
}

It should look like this on running the project.

Concept

Assuming that reader knows about contentOffset and contentInset.
But actually contentOffset is a CGPoint aka a pointer which tells the content position in frame from X and Y direction and contentInset is Space/Padding you can give either on top and bottom in vertical flow layout else left or right in horizontal flow layout in the collection view.

So depending upon pagination case we will add subview. In that subview there is UIActivityIndicatorView or we can say loader, which will rotate when the view will be visible. As shown below the visuals of refresh all and load more.

Pull To Refresh i.e. Refresh All

Load More

Let’s began with creating manager class name HorizontalPaginationManager. This class will handle pagination actions. It would be good practice to add managers to handle some usual actions. It makes code reusable.

Code Initiation

So I’ll explain the step by step

1. Add above mention variables in your manager class from Line no.19–27.
2. isLoading tells whether loading is going or not. It helps to avoid duplicate requests.
3. isObservingKeyPath helps in observing the change in content offset. It helps to check threshold distance from where we call refresh all or load more. In de-initialiser, the observer is removed.
4. scrollView is taken as a superclass variable Though it is not required. We will add above-mentioned observer on this variable.
5. leftmost/rightmost views are the views we will add on the basis of action i.e. left one for refresh all and the right one for load more. This view visibility denotes that action is processing.
6. Rest are colours used as per requirement for customisation.
7. Add a delegate of type HorizontalPaginationManagerDelegate. This need to get te actions which needed to perform while pagination. This protocol consists of two methods as per the actions required. trailing closures are required in order to remove loader views and reset the pagination actions in order to use it again.
8. init() aka initialiser required scrollView majorly your collection view.

Now you have to setup leftmost/rightmost views as above mentioned, In both the case I have added activity indicator. Set scrollView inset left/right respectively on the basis of view width. Also when the action is performed completely, we have to assign nil and remove from scrollView so that we don’t get duplicates.

Observing Offset

Now you have to override observeValue for keyPath method like above. Mention key contentOffset and set condition for .new value so that we will get lastest changed value. On observing we'll call setContentOffSet as mentioned in above. So in that, there will be 2 conditions.

1. if offsetX < -100 && !self.isLoading: which means if you dragged beyond -100 the threshold value && it is not loading then you will perform the action for refresh all and you have to set self.isLoading to true so it will be called once. Followed by you will call refresh all delegate method in which it’s callback will reset value for loading. It will remove left most view and self.isLoading to false.
2. if contentWidth > frameWidth, offsetX > (diffX + 130) && !self.isLoading: which means if you have your content size is greater than you scrollView frame size && dragged beyond 130 the threshold value && it is not loading then you will perform the action for load more and you have to set self.isLoading to true so it will be called once. Followed by you will call load more delegate method in which it’s callback will reset value for loading. It will remove left most view and self.isLoading to false.
3. The final part is set up pagination in your ViewController class.

Here I called fetchItems method in viewDidLoad as initially, we want to load items initially without pagination actions. Added delay in order to feel like API calls. Like I said earlier refresh all will reset data i.e. sets fresh data and load more append data in the same content.

I hope you like this tutorial. Feel free to reach out 😄 😄 😄!!!
Nickelfox

Attached Demo Project

Abhishek9634/HorizontalPaginationDemo

H A P P Y — C O D I N G 😄 😄 😄!!!

Here is my other two recent stories…

iOS Swift Expandable TextView with Placeholder

iOS Swift Custom TabBarController with Tab Item Animation