View SDK Observations and Expectations
I'm looking for an open source PDF custom viewer for our web application along with the capability of saving PDF with annotations. I'm glad to found the solution (Though its cloud based) from the leader. With 2 days of knowledge from your documentation and other posts, I'm posting my observations and questions:
- View SDK is free to use. This is mentioned in blog and forum posts. But if it mentioned clearly in documentation page, whats free and whats not then it will be very helpful.
- View SDK is free now. Its great but will it remain same in future ?
- Free View SDK includes annotation tools and callback APIs (Like save, user profile etc...) ?
- We understand from the exisitng posts in forum that you are collecting events information for analytics. We are OK that you are NOT collecting any user related/generated information. But whats the need of collecting our app URL (externalUserId in post body of https://dc-api.adobe.io/system/log)
- As per posts in the forum, lot of new changes/enhancements in road map in this year like drawing shapes annotation tool etc... Please publish the road map document. It will be helpful for us alot.
- It will be good to have annotation tools in all the modes.
- Forcing <CLIENT_ID> for localhost web application may not be required. Only if you want users to create account in adobe.
- Any plans of View SDKs for native mobile apps (iOS, Android) ?
- Any plans of supporting offline web applications ?
- There is no concept of versions as we are using cloud SDKs or Any plans of providing version wise cloud SDKs ? So,
- Any new change/enhancement in SDK/UI will reflect immediately in our web application. It will be good to have them immediately but Clients may get confused for significant UI changes.
- There will be no change in the existing callback APIs in future ?
