What's New in This Release?

This release of the Client SDK for macOS contains bug fixes and stability enhancements for a seamless user experience. In addition, it includes the following features:

Manually Bridging USB Devices

If you need to support more than 20 USB devices, or if you expect your users to control which devices can be bridged, they can be manually added by opening the client’s USB Devices menu and enabling them.

The following table contains a brief description of the header files included in the Anyware Client SDK for macOS:

Linking the SDK for macOS

This section includes instructions for linking the SDK libraries with your custom client application:

1. Open a Terminal window and change directory to the root of the mounted SDK disk image.

2. Copy the SDK files to desired location for SDK development, refered to as <sdk_location> below.

   CMake modules location

Limits on Customization

The macOS has elements which are part of the operating system user interface and cannot be modified programmatically, as described in the following sections.

macOS Limitations

The following run-time limitations are enforced by macOS on the application menu (beside the menu apple icon menu):

Anyware Client SDK for macOS 25.03

The Client SDK for macOS provides developers tools to create a custom Anyware client with a unique user interface and workflow, or to embed a PCoIP session into another program or solution. Clients built with the SDK can connect to remote desktops using Anyware agents or Remote Workstation Cards.

The SDK is provided as part of HP Anyware by special agreement with HP.

Establishing a PCoIP Session

Before you can establish a PCoIP session with a host desktop, gather the following host desktop details:

Frequently Asked Questions

The following are answers to commonly asked questions when contemplating how to develop custom Anyware Clients using the Teradici Anyware Client SDK.

Q: Can I brand the pre-session client with my company logo and colors?

The following PCoIP session features can be customized:

• Session Menu bar Visibility
• Disable Hot Keys
• Windowed or Fullscreen Mode
• Set Host Resolution
• Custom Client Branding
• Image Scaling
• Maintain Aspect Ratio
• USB Auto Forward
• USB VID/PID Auto Forward
• Disable USB
• Locale
• Session Log ID
• Log Level
• Log Folder
• Log Prefix
• Force Native Resolution

Creating a Branding Text Layout File

The layout file format used to customize the session client is an UTF-8 XML text file. The layout schema is a top-level <pcoip-client-branding/> element with a version attribute describing the schema version, and containing the required elements described next: