Build Windows apps
that were made for the browser.
Any Windows app can be streamed untouched. When you own the code, link the Onscryn SDK and the app starts to take part: it hands over its own picture, receives input directly, and exposes functions that workflows can call.
What a linked app
can do.
Streams from the inside
Your app hands Onscryn its own picture and receives mouse and keyboard in its own window. No screen scraping, and a few calls to wire up.
Callable by workflows
Register named actions such as getOrder or approveInvoice. Workflows, webhooks and schedules call them and get JSON back, even with no browser open.
Native-feeling hand-offs
Send a PDF or a link to the user's browser, receive uploads and dropped files, sync the clipboard, and print to the printer they actually have.
A UI tree for free
The SDK publishes your app's controls through UI Automation. That powers selectable text, search, and the workflow builder's element picker.
A few calls,
not a rewrite.
The SDK is a native library with a flat C interface, so it works from C, C++, C# and VB.NET. Your app keeps its code, its behavior and its data model.
- 01
Add the library
Put Onscryn.Capture.dll beside your app. C and C++ use the header, and C#, VB.NET and others call it natively.
- 02
Start and send frames
Call Onscryn_Start once, then hand over a picture whenever your window changes.
- 03
Test on your machine
A file-dump mode writes each frame to a bitmap, so you can check it without a server.
- 04
Register and launch
Add the app in Admin, choose SDK capture, and open it from the catalog.
OnscrynOptions opts = {}; // zero = auto input + auto UI tree
opts.instanceId = argv[1]; // passed in by the host
opts.transport = ONSCRYN_TRANSPORT_PIPE;
opts.tileQuality = 80;
Onscryn_Start(&opts);
// a named action workflows can call
Onscryn_RegisterAction("getOrder", "One order (params: id)", GetOrder, nullptr);A pattern, not a drop-in. The quick start has full examples in C# and C++.
How it fits together.
The picture and the people
01
Your app, with the SDK
Draws its own window and hands the picture over.
02
Onscryn on your host
Streams it and applies your clipboard, file and watermark rules.
03
A browser tab
Shows the app. Mouse, keys, uploads and drops go back.
Automation
01
A workflow, webhook or schedule
Runs on demand or on a timer.
02
Onscryn
Starts a session, even with no browser attached.
03
A named action in your app
A function you registered. Returns JSON.
Docs, guides and notes.
- DocsSDK overviewWhat it is and what a linked app gets.
- DocsQuick startFrom nothing to a window in a browser tab.
- DocsNamed actionsYour app as an API for workflows.
- DocsAPI referenceEvery function, callback and option.
- GuideBuild a Windows app that streamsThe decisions and the steps.
- GuideSDK or generic captureWhich to choose, per application.
- PostA streamed app should take partWhy cooperating beats being watched.
- PostAn API from the insideNamed actions, and what a few of them unlock.
Build Windows apps with the Onscryn SDK
How to build or adapt a Windows app so it streams to a browser, takes part in the stream, and exposes functions that workflows can call.
- DocsThe SDK overview
- DocsSDK quick start: your first streamed app
- DocsHow your app is launched and starts the SDK
- DocsDrawing and sending frames
- DocsInput, the UI tree and building for automation
- DocsNamed actions: your app as an API
- DocsFiles, clipboard, printing and links
- DocsDeploy, tune and troubleshoot an SDK app
- DocsSDK API reference
- GuideHow to build a Windows app that streams to a browser
- GuideTurn a Windows app into an API with named actions
- GuideDesign a Windows app so UI automation just works
- GuideSDK app or generic capture: which should you choose?
- PostA streamed app should take part, not just be watched
- PostGive your legacy app an API from the inside
Want the SDK package?
It is provided on request. Write to [email protected] and tell us what you are building.