"Solution Builder" is the term used to describe the ScreenPal support for Clients who license ScreenPal to use with their own products and services. If you are interested in licensing ScreenPal Solution Builder, please Contact Sales.

For example, Clients have their website offer to download and run the ScreenPal screen recorder application for their customers to capture videos, which are then uploaded to the Client's servers to provide their customers products and services using those videos.

For the the ScreenPal Team to provide the Solution Builder service to Clients, several ScreenPal components are used. These include the ScreenPal Installers, JavaScript for Client webpages, and the ScreenPal application.

The Solution Builder ScreenPal Installers provide alternative conditional behavior on top of the standard ScreenPal Installers. For example, the Installer runs silently, except at the end of the installation when a pop-up is displayed to tell the user to go back to the webpage to launch ScreenPal.

ScreenPal provides JavaScript, referred to as the "Basic Uploader", that Clients can use and customize to download the appropriate Solution Builder Installer and then launch the ScreenPal screen recorder application. For example, when launching ScreenPal, the Clients can pass their customizations by altering the JavaScript code and in a properties file inside a JAR file that is passed to the ScreenPal application.

A Solution Builder Client may also supply a "Custom Uploader", which is customized Java UI in a reserved section of the ScreenPal Upload UI panel. For more information, see Custom Uploader.

The Client's webpage runs Solution Builder Basic Uploader JavaScript to detect if ScreenPal is installed and offers to download the Solution Builder Installer if not. The JavaScript then launches ScreenPal with a special URL protocol launcher that provides Client customization properties to ScreenPal. ScreenPal alters its behavior and user interface based on those Client properties and uploads videos to the specified location.

Clients who licensed the older versions of Solution Builder, referred to as versions "JRE7" and "JRE14", can upgrade their license to the newer "JRE19" version. This migrates from older Screencast-O-Matic application to the newer ScreenPal application. Here are some benefits of the newer ScreenPal "JRE19" version of Solution Builder:

See the Migrating to a Newer Solution Builder Version document for how a Client can migrate from older "JRE7"/"JRE14" to newer "JRE19" version.

A Client's Customer goes to the Client's webpage. They click a link/button to initiate the capture of a video of their desktop activity. The webpage runs the Basic Uploader JavaScript supplied from ScreenPal and customized by the Client. The Basic Uploader looks for a cookie that specifies if ScreenPal has been installed. If it has not been installed, then it offers for download the ScreenPal Installer. Alternatively, the Basic Uploader can just try to launch ScreenPal with the Launcher URL Protocol and detect a timeout to know that ScreenPal has not been installed. A downloaded ScreenPal Installer is run by the Client's Customer. The Installer runs silently and does not require Customer interaction, except a window popup message at the end that the Customer must dismiss. The message is similar to, "Screen Recorder Ready! Go back to the webpage to start a recording." Once the Client's Customer dismisses the Installer notification, they go back to the Client's webpage and click a link/button to launch ScreenPal. ScreenPal is launched with the operating system registered Launcher URL Protocol, which is a string, like screen-recorder-launcher-jre19://ScreenRecorder?.... The operating system launches ScreenPal and passes it that URL, which contains parameters for ScreenPal that identify the Client's desired ScreenPal version and their Solution Builder customization option choices. ScreenPal launches its Recorder to allow the Client's Customer to make a video recording. When the recording is completed, the ScreenPal Upload UI panel is displayed, and has the Client's customized options respected. The Client's customization may allow the ScreenPal Editor/Manager to be used before the Client's Customer revisits the Upload UI panel to initiate the upload of their finalized video. The Client's customizations specify where the video is uploaded. The Client's webpage is revisited to then offer the Client's Customer access to the Client's products and services, using the video they just uploaded.

The ScreenPal Team has created a test environment for potential Solution Builder Clients to try out ScreenPal Solution Builder before purchasing a license. The potential Client does not need to configure anything. The test environment is self contained and available for anyone to use.

Potential Clients may go to https://screenpal.com/api/example/basicuploader-JRE19 to run that webpage's BasicUploader JavaScript to try out the Client Solution Builder experience. Expect the experience described in the section above.

Also see