<aside> <img src="/icons/chat_yellow.svg" alt="/icons/chat_yellow.svg" width="40px" /> An introduction to the connected Handy and the Handy SDK.

</aside>

Handy SDK

The Handy SDK is a collection of functions and examples intended to simplify Handy interfacing and app development. It is built on top of the Handy API v2 . Before we dive into the methods of the Handy SDK , it is important to understand the basics of Handy connectivity.

The Connected Handy

As a connected device, The Handy can be controlled over the Internet. A client can send commands to our central Handy servers, which will then relay the command to a specific Handy device.

Handy masturbators are identified by their Connection Key — which is uniquely generated inside the Handy itself. In essence, if you have a Connection Key and a corresponding Handy connected to the Internet, you can send commands to the Handy masturbator through the open Handy API v2.

This enables Handy masturbator to interact with a wide variety of media, including videos, games, and web apps.

Our own first-party apps like the remote control and the local video player are built on top of the Handy API v2 .

Adult video providers have also leveraged the Handy API v2 to create more immersive and satisfying experiences on their own platforms — in fact, you can find a list of video partners that have integrated the Handy with their videos here.

Do you own or work with a video site? Check out our Video site - value proposition!

Video Synchronization

While the Handy masturbator can receive arbitrary speed and position commands, it can also chain commands together to create a smooth flow of stroking movement. The most common use case for this is synchronizing Handy movement with adult video.

The Handy masturbator accepts CSV files containing time and position coordinates that tell the Handy where to move the slider at a corresponding time. While the Handy can execute the commands inside the CSV file independently, our SDK provides a simple interface for binding Handy motion to a <video> element.

Modes

The Handy uses modes to separate different functions. It has modes directly corresponding to three protocols:

• Handy Alternate Motion Protocol (HAMP) — the mode to control the speed and stroke length of the oscillating Handy motion.
• Handy Direct Streaming Protocol (HDSP) — an experimental mode that tells the Handy where to go and how fast to arrive there.
• Handy Synced Stream Protocol (HSSP) — the mode used for synchronizing the Handy with videos and scripts.

Certain operations are only available when the Handy is set to a corresponding mode. For instance, functions such as script looping are only possible when the Handy is synchronized with a script — that is, the Handy is in HSSP mode.

See the SDK Reference for details.