onscryn

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.

  1. 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.

  2. 02

    Start and send frames

    Call Onscryn_Start once, then hand over a picture whenever your window changes.

  3. 03

    Test on your machine

    A file-dump mode writes each frame to a bitmap, so you can check it without a server.

  4. 04

    Register and launch

    Add the app in Admin, choose SDK capture, and open it from the catalog.

Start the SDK and register an actionC++
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

  1. 01

    Your app, with the SDK

    Draws its own window and hands the picture over.

  2. 02

    Onscryn on your host

    Streams it and applies your clipboard, file and watermark rules.

  3. 03

    A browser tab

    Shows the app. Mouse, keys, uploads and drops go back.

Automation

  1. 01

    A workflow, webhook or schedule

    Runs on demand or on a timer.

  2. 02

    Onscryn

    Starts a session, even with no browser attached.

  3. 03

    A named action in your app

    A function you registered. Returns JSON.

The same app serves both: people through the browser, and automation through the functions it chooses to expose.

Want the SDK package?

It is provided on request. Write to [email protected] and tell us what you are building.

Want it set up
with you?