SDK app or generic capture:
which should you choose?
When you register an application on Onscryn you choose how it is captured. The choice is per application, it is easy to change your mind, and getting it right mostly comes down to whether you can change the app and what you want from it.
By the Onscryn team · Published · 6 min read
What each one is
Generic capture streams an application without any cooperation from it. The agent captures its window from outside and sends input in from outside. Nothing in the app changes, which is why it suits packaged software and anything you do not own.
An SDK app links the Onscryn library and takes part. It hands over its own picture, receives input in its own window, publishes its UI tree and can register functions for workflows to call.
How to choose
Ask these in order.
- Can you modify the application and rebuild it? If not, use generic capture.
- Do you want workflows to call functions rather than click screens? If so, use the SDK.
- Does the app need to hand files, links or printouts to the user's browser? The SDK has direct calls for each.
- Is it a quick pilot? Generic capture is faster to start, so begin there and move later if you need more.
| SDK app | Generic capture | |
|---|---|---|
| Changes to your app | You link the library and add a few calls | None. The app is untouched |
| How the picture is made | The app hands over its own window picture | The agent captures the app's window from outside |
| Mouse and keyboard | Posted into the app's own window by the SDK | Sent in by the agent from outside |
| UI tree for workflows | Read from inside the app | Read from outside the app |
| Named actions | Yes: workflows call functions you register | No: workflows click and type |
| Files, links and clipboard from the app | Direct calls: SendFile, OpenUrl, SendClipboard | Through the viewer's own upload, download and clipboard controls |
| Best for | Software you build or can modify | Software you cannot change |
| Licensing | Unchanged: Windows and the app still need their own licences | Unchanged: Windows and the app still need their own licences |
What changes in the work
Generic capture is a registration. The SDK is a small amount of development: start the library, hand over frames, and optionally register actions. A first working stream is usually a short session, and the quick start walks through it.
Mixing them
Nothing forces one choice for the whole organization. A common pattern is generic capture for the vendor packages and the SDK for the one in-house app that people automate most. The settings, access rules and data controls are the same for both.
What is the same either way
Both run on a host you control, in a session of their own. Both get sign-in, roles, clipboard and file controls, watermarking, recording and the UI tree for workflows. Neither changes licensing, so Windows and the application still need valid licences.
Questions.
Yes. The capture mode is a setting on the application. Ship a build that links the SDK, point the entry at it and change the mode.