You can certainly keep it in the application, but again, it's non-trivial if you want high-level PDF navigation, which in this case requires Cocoa. The fact that you're using a webview suggests you're not Cocoa-capable.
Having the skills is a good thing, of course, but I took your question as looking for a solution today that is within your means.
I'm trying to get you to take an approach now that will let you get on with delivering the information and possibly provide time while you sharpen your skills.
I'd think tho (with the info about the rest of the app and using a WebView to display the PDF) that unless you can as an example adopt the JS in the linked app, your only choice is to delay the 500+ page PDF until your skills come up. No doubt such a comprensive app would have value at that point, but the catalogs will be outdated and you may have left school by that time 🙂. Having an opportunity to make a profit isn't much of an opportunity if it requires significant skills that don't yet exist.
There's no free lunch...either stick with low-impact WebViews, etc. or start cracking the Obj-C & Cocoa books.