Question
[Embed API] Please improve the developer experience
The embedded PDF viewer is a really nice and valuable product. I chose it over pdf.js for its reliability and over commercial solutions for its free availability, and I assume many others will come to a similar conclusion.
Now that I have started experimenting with it, there are several things that make me rather uncomfortable as a developer to invest a lot of effort into it. I hope Adobe will consider some of the following suggestions, all of which are pretty much standard for professional offerings nowadays.
- Proper API reference
The current API documentation comes in the form of a How-To. What we really need is a complete, standardized reference of all available methods in the library. Otherwise I can't deal with potential exceptions and the like. - Versioned API
Currently, I have to load the library from an unversioned link (https://documentservices.adobe.com/view-sdk/viewer.js). This way I have no good means to implement workarounds for current issues, let alone deal with API changes. - Developer API keys
API keys currently can only be registered for TLDs or localhost. But developers are often working with servers hosted on local IP addresses or local DNS names. Please make it possible to register API keys for these as well. - NPM package
A downloadable NPM package would help with dependency and version management, improve performance and reliability, and integrate better with UI frameworks. Other closed-source/API key solutions like Pdftron can do it, so why can't Adobe? - TypeScript typings
More of a convenience factor, but this is also standard these days. - Issue tracking
This support community is nice, but it really is a very basic forum that doesn't provide a good overview of current issues.
Thank you for your consideration. 🙂
AdChoices