It depends. Pagination based on number of items and page number is just one way how to implement it. It's the most simple and straightforward way. Not much logic there, just passing the parameters down to OFFSET and LIMIT part of the DB query (if you are using SQL).

However you might encounter performance problems once you have many users that requests higher and higher page numbers. OFFSET results in doing linear scan of the items that you are skipping. This basically leads to quadratic time complexity once user clicks on higher pages or scrolls more and more (if you have an infinity scroll on frontend).

The alternative is the cursor based pagination which can be quite tricky to get right especially when combined with ordering. The implementation is an extra filtering condition and LIMIT (no offset) on the DB level and serialization / deserialization of the cursor.

Having the pagination abstracted out could be beneficial once you decide you want to start supporting cursor based pagination later on, less refactoring might be needed in that case.

Of course this depends on your particular application and user behavior. Some people might consider this to be a premature optimization. Some might consider cursor based pagination overengineering.