What It Covers
Add wireless casting to your display product. Without starting from scratch.
DisplayNote's Wireless Casting SDK gives hardware manufacturers and software developers a ready-to-integrate layer for AirPlay, Google Cast and Miracast, built, maintained and supported by the team behind Screen Sharing.
From Friction to Flow
Sharing Built In
What It Covers
Add wireless casting to your display product. Without starting from scratch.
DisplayNote's Wireless Casting SDK gives hardware manufacturers and software developers a ready-to-integrate layer for AirPlay, Google Cast and Miracast, built, maintained and supported by the team behind Screen Sharing.
What It Covers
Add wireless casting to your display product. Without starting from scratch.
DisplayNote's Wireless Casting SDK gives hardware manufacturers and software developers a ready-to-integrate layer for AirPlay, Google Cast and Miracast, built, maintained and supported by the team behind Screen Sharing.
From Friction to Flow
Sharing Built In
Built for teams who need wireless casting in their product, not as a side project.
Who It's For
The DisplayNote SDK is for:
Display hardware manufacturers building wireless casting into Android or Windows display products, where reliability, certification support and long-term vendor commitment matter.
AV and UC platform developers: software teams who need to add protocol-complete wireless casting to an existing product without building and maintaining the protocol layer in-house.
System integrators and specialist developers: teams delivering custom room experiences that include wireless casting as one layer of a broader deployment.
Built for teams who need wireless casting in their product, not as a side project.
The SDK is designed to integrate with existing product architectures. SDK access sits within the broader DisplayNote display vendor programme.
Who It's For
The DisplayNote SDK is for:
Display hardware manufacturers building wireless casting into Android or Windows display products, where reliability, certification support and long-term vendor commitment matter.
AV and UC platform developers: software teams who need to add protocol-complete wireless casting to an existing product without building and maintaining the protocol layer in-house.
System integrators and specialist developers: teams delivering custom room experiences that include wireless casting as one layer of a broader deployment.
Built for teams who need wireless casting in their product, not as a side project.
The SDK is designed to integrate with existing product architectures. SDK access sits within the broader DisplayNote display vendor programme.
Who It's For
The DisplayNote SDK is for:
Display hardware manufacturers building wireless casting into Android or Windows display products, where reliability, certification support and long-term vendor commitment matter.
AV and UC platform developers: software teams who need to add protocol-complete wireless casting to an existing product without building and maintaining the protocol layer in-house.
System integrators and specialist developers: teams delivering custom room experiences that include wireless casting as one layer of a broader deployment.
Protocol-complete wireless casting, ready to integrate.
The DisplayNote SDK provides receiver-side support for:
What It Covers
AirPlay
Receiver implementation for Apple device casting, including Touchback support for iPad interaction from the display.
Google Cast
Receiver implementation for Android and Chrome device casting.
Miracast
Receiver implementation for Windows and Android device casting, including optional MICE (Miracast over Infrastructure Connection Establishment) support for deployments where it has been implemented at the firmware level.
The SDK is built on the same codebase as Screen Sharing. That means the protocol implementations are production-tested in live deployments across classrooms, meeting rooms and display vendor hardware products, not experimental or prototype-grade.
Protocol-complete wireless casting, ready to integrate.
The DisplayNote SDK provides receiver-side support for:
What It Covers
AirPlay
Receiver implementation for Apple device casting, including Touchback support for iPad interaction from the display.
Google Cast
Receiver implementation for Android and Chrome device casting.
Miracast
Receiver implementation for Windows and Android device casting, including optional MICE (Miracast over Infrastructure Connection Establishment) support for deployments where it has been implemented at the firmware level.
The SDK is built on the same codebase as Screen Sharing. That means the protocol implementations are production-tested in live deployments across classrooms, meeting rooms and display vendor hardware products, not experimental or prototype-grade.
Protocol-complete wireless casting, ready to integrate.
What It Covers
AirPlay
Receiver implementation for Apple device casting, including Touchback support for iPad interaction from the display.
Google Cast
Receiver implementation for Android and Chrome device casting.
Miracast
Receiver implementation for Windows and Android device casting, including optional MICE (Miracast over Infrastructure Connection Establishment) support for deployments where it has been implemented at the firmware level.
The SDK is built on the same codebase as Screen Sharing. That means the protocol implementations are production-tested in live deployments across classrooms, meeting rooms and display vendor hardware products, not experimental or prototype-grade.
Available for the platforms hardware partners actually build on.
Platform Support
Android
Including firmware-integrated APK deployment for Android displays, with EDLA certification support.
Windows
For Windows-based meeting room displays and UC devices.
ChromeOS
Via the Android runtime on supported Chromebooks and ChromeOS-based displays.
Linux
Can be supported upon request.
Available for the platforms hardware partners actually build on.
Platform Support
Android
Including firmware-integrated APK deployment for Android displays, with EDLA certification support.
Windows
For Windows-based meeting room displays and UC devices.
ChromeOS
Via the Android runtime on supported Chromebooks and ChromeOS-based displays.
Linux
Can be supported upon request.
Available for the platforms hardware partners actually build on.
Platform Support
Android
Including firmware-integrated APK deployment for Android displays, with EDLA certification support.
Windows
For Windows-based meeting room displays and UC devices.
ChromeOS
Via the Android runtime on supported Chromebooks and ChromeOS-based displays.
Linux
Can be supported upon request.
Why Build With Us
What you get beyond the protocol implementation.
Wireless casting protocols are not static. AirPlay, Google Cast and Miracast change. Certification requirements change. Device behaviour changes. Hardware partners building on a third-party casting implementation are effectively taking a dependency on the quality of that implementation over time.
In-house protocol expertise
The SDK is built and maintained by the same team that develops Screen Sharing. No third-party protocol layer sitting below the integration.
Production testing at scale
Certification pathway support
Long-term commercial commitment
White-label availability
Why Build With Us
What you get beyond the protocol implementation.
Wireless casting protocols are not static. AirPlay, Google Cast and Miracast change. Certification requirements change. Device behaviour changes. Hardware partners building on a third-party casting implementation are effectively taking a dependency on the quality of that implementation over time.
In-house protocol expertise
The SDK is built and maintained by the same team that develops Screen Sharing. No third-party protocol layer sitting below the integration.
Production testing at scale
Certification pathway support
Long-term commercial commitment
White-label availability
Why Build With Us
What you get beyond the protocol implementation.
Wireless casting protocols are not static. AirPlay, Google Cast and Miracast change. Certification requirements change. Device behaviour changes. Hardware partners building on a third-party casting implementation are effectively taking a dependency on the quality of that implementation over time.
In-house protocol expertise
The SDK is built and maintained by the same team that develops Screen Sharing. No third-party protocol layer sitting below the integration.
Production testing at scale
Certification pathway support
Long-term commercial commitment
White-label availability
Integration, not a project.
The SDK is designed to integrate with existing product architectures, not require a rebuild around it.
How It Works
1.
Receiver implementation available as an Android APK or Windows library.
2.
Documentation, sample code and technical onboarding provided.
3.
Partner support from the DisplayNote technical team throughout integration and at launch.
4.
Ongoing version updates aligned to protocol changes and certification requirements.
The typical integration path starts with a technical conversation, moves to documentation review and a proof-of-concept phase, then proceeds to production integration with partner technical support.
Integration, not a project.
The SDK is designed to integrate with existing product architectures, not require a rebuild around it.
How It Works
1.
Receiver implementation available as an Android APK or Windows library.
2.
Documentation, sample code and technical onboarding provided.
3.
Partner support from the DisplayNote technical team throughout integration and at launch.
The typical integration path starts with a technical conversation, moves to documentation review and a proof-of-concept phase, then proceeds to production integration with partner technical support.
Integration, not a project.
The SDK is designed to integrate with existing product architectures, not require a rebuild around it.
How It Works
1.
Receiver implementation available as an Android APK or Windows library.
2.
Documentation, sample code and technical onboarding provided.
3.
Partner support from the DisplayNote technical team throughout integration and at launch.
The typical integration path starts with a technical conversation, moves to documentation review and a proof-of-concept phase, then proceeds to production integration with partner technical support.
SDK access sits within the broader DisplayNote display vendor programme.
The Programme
SDK access is available as part of the DisplayNote display vendor programme, which includes:
SDK licensing and technical onboarding.
White-label receiver and client branding options.
Co-marketing and GTM support for qualified partners.
Named partner support and escalation.
Access to DisplayNote technical and commercial teams throughout the partnership.
AirPlay support, available as a paid add-on, is purchasable directly through Central Manager for Screen Sharing deployments. For SDK integrations, AirPlay licensing terms are confirmed as part of the partner onboarding process.
SDK access sits within the broader DisplayNote display vendor programme.
The Programme
SDK access is available as part of the DisplayNote display vendor programme, which includes:
SDK licensing and technical onboarding.
White-label receiver and client branding options.
Co-marketing and GTM support for qualified partners.
Named partner support and escalation.
Access to DisplayNote technical and commercial teams throughout the partnership.
The two outcomes reinforce each other. When the room is easier to use, it becomes easier to support.
SDK access sits within the broader DisplayNote display vendor programme.
The Programme
SDK access is available as part of the DisplayNote display vendor programme, which includes:
SDK licensing and technical onboarding.
White-label receiver and client branding options.
Co-marketing and GTM support for qualified partners.
Named partner support and escalation.
Access to DisplayNote technical and commercial teams throughout the partnership.
The two outcomes reinforce each other. When the room is easier to use, it becomes easier to support.
Trusted Worldwide
Already deployed in hardware from leading display manufacturers.
Screen Sharing, and the protocol implementations it shares with the SDK, is already embedded in hardware from Newline, Dell, Clevertouch, Avocor, Sharp, Samsung and others.
That is the reference point for hardware partners evaluating the SDK: not a preview capability, but an integration already running at scale in commercially released products.
Trusted Worldwide
Already deployed in hardware from leading display manufacturers.
Screen Sharing, and the protocol implementations it shares with the SDK, is already embedded in hardware from Newline, Dell, Clevertouch, Avocor, Sharp, Samsung and others.
That is the reference point for hardware partners evaluating the SDK: not a preview capability, but an integration already running at scale in commercially released products.
Trusted Worldwide
Already deployed in hardware from leading display manufacturers.
Screen Sharing, and the protocol implementations it shares with the SDK, is already embedded in hardware from Newline, Dell, Clevertouch, Avocor, Sharp, Samsung and others.
That is the reference point for hardware partners evaluating the SDK: not a preview capability, but an integration already running at scale in commercially released products.
FAQs.
Common Questions
Which platforms does the DisplayNote SDK support?
What protocols does the DisplayNote Casting SDK support?
Which platforms does the Casting SDK run on?
Does the SDK support EDLA certification for Android display hardware?
Is white-label branding available with the Casting SDK?
What does the integration process look like?
How is the Casting SDK different from just deploying Screen Sharing?
FAQs.
Common Questions
Which platforms does the DisplayNote SDK support?
What protocols does the DisplayNote Casting SDK support?
Which platforms does the Casting SDK run on?
Does the SDK support EDLA certification for Android display hardware?
Is white-label branding available with the Casting SDK?
What does the integration process look like?
How is the Casting SDK different from just deploying Screen Sharing?
FAQs.
Common Questions
Which platforms does the DisplayNote SDK support?
What protocols does the DisplayNote Casting SDK support?
Which platforms does the Casting SDK run on?
Does the SDK support EDLA certification for Android display hardware?
Is white-label branding available with the Casting SDK?
What does the integration process look like?
How is the Casting SDK different from just deploying Screen Sharing?
If you are building a product that needs wireless casting, the right next step is a direct conversation.
If you are building a product that needs wireless casting, the right next step is a direct conversation.
If you are building a product that needs wireless casting, the right next step is a direct conversation.
Solutions
Technical Support
Resources
Contact
Solutions
Technical Support
Resources
Contact
Solutions
Technical Support
Resources
Contact
Solutions
Technical Support
Resources
Contact