[justin_oaks]

I agree that the author wasn't quite clear on this point.

If you control both the client and the API, then pagination is something you can add in later. But setting up pagination early may make sense if the client isn't in your control.

The author gave the example of the an old mobile app that users don't update. The client is also out of your control if it's a public API that users call with whatever client code they choose.

That said, I'm not sure how setting up "fake" pagination is helpful if the client isn't already coded to use pagination responses from the server. So I'll have to assume the author means that any client you provide already has pagination logic built-in.