PaperKit: Correct approach for multi-page or infinite-canvas documents?

I’m trying to figure out how to extend PaperKit beyond a single fixed-size canvas.

From what I understand, calling PaperMarkup(bounds:) creates one finite drawing region, and so far I have not figured out a reliable way to create multi-page or infinite canvases.

Are any of these correct?

  • Creating multiple PaperMarkup instances, each managed by its own PaperMarkupViewController, and arranging them in a ScrollView or similar paged container to represent multiple pages?
  • Overlaying multiple PaperMarkup instances on top of PDFKit pages for paged annotation workflows?
  • Or possibly another approach that works better with PaperKit’s design?

I mean it has to be possible, right? Apple's native Preview app almost certainly uses it, and there are so many other notes apps that get this behavior working correctly, even if it requires using a legacy thing other than PaperKit.

Curious if others have been able to find the right pattern for going beyond a single canvas.

PaperKit: Correct approach for multi-page or infinite-canvas documents?
 
 
Q