Desktop and line-of-business applications
Put document output inside the application your users already have open
Preview, print, export and fill — inside a desktop application, with no server round trip and no internet dependency.
The problem
Desktop software is expected to preview and print documents that look exactly like what gets filed. Delegating that to a web service adds a network dependency to a feature users expect to work on a train.
The approach
Link the engine into the application. Render pages to a bitmap for preview, produce the same file for export, and use the platform print path — all in the process the user is already in.
How you can check it
The viewer and rendering APIs are documented and counted in the capability pages, and the desktop examples ship in the download for the native packages.
- Windows C/C++
- .NET (source P/Invoke)
- NuGet package
- Delphi / Object Pascal
- macOS
- Windows ActiveX / COM
- Rendering & Viewer (130 APIs)
- Printing (17 APIs)
- Forms (115 APIs)
- Annotations (95 APIs)
The capability areas behind it
Prove it on your own documents
Public download, no account. Run it against the files you actually have before anyone signs anything.