Introducing the New Inverse Installer 2.0: A Comparative Guide to Haply's APIs
The Inverse Installer 2.0 is the latest and most feature-packed software available to run the Inverse3 device. It is robust, and future-proofed with all of our latest features and product name changes.
This article explains the difference between HardwareAPIs and Inverse Installer 2.0. It recommends why you might use one over the other, provides a side-by-side comparison of the two architectures, and explains what you need to consider when upgrading to version 2.0.
Which software should I download to run my Inverse3 device?
If you are starting from scratch, we recommend downloading the Inverse Installer 2.0, which includes:
Inverse SDK
Documentation and tutorials
Runtime libraries
This SDK is the latest and most feature-packed software available for the Inverse3 device. It is robust, future-proof, and includes all official product name updates.
Additional improvements include:
Bug fixes that reduce interference with haptic devices
Runtime architecture that handles:
Device management
Automatic device discovery
Device pairing
Multiple client support
Device connection logging
Forward compatibility with future features
Our team highly recommends upgrading to the 2.0 SDK.
Note:
The API supports C and C++ and is currently available only for Microsoft Windows. Support for additional operating systems will be released in the coming months.
When or why should I use the HardwareAPIs?
HardwareAPIs are recommended if your system is not running Windows. These APIs still use the older product names, such as Handle (now renamed to VerseGrip).
HardwareAPI C++
The most complete direct Hardware API with support for:
Windows
Linux
macOS
aarch64
HardwareAPI Python
Offers the same functionality as the C++ version and is especially popular among students and robotics developers who prefer Python.
Supported platforms include:
Windows
Linux
macOS
aarch64
When or why should I use the Inverse SDK Integrations?
The Inverse SDK for Unity allows developers to build basic haptic integrations inside the Unity Game Engine with a low technical barrier.
The SDK includes:
Tutorials
Documentation
Unity Package Manager support
It is ideal for learning haptics and creating your first scenes.
However, for high-performance haptic physics simulation, Unity's native physics engine is not recommended, because it cannot maintain the 1000 Hz closed-loop communication required for high-quality haptics.
If you have any questions, contact support@haply.co.
Updating to the Inverse Installer: Advantages and Changeover
The Inverse Installer introduces a service layer that automatically manages:
Device auto-discovery
Device pairing
Device port management
This eliminates manual port management and simplifies development.
Architecture Advantages of the Inverse Installer (Compared to HardwareAPIs)
Device management
Automatic device discovery
Device pairing
Multiple client support
Support for future features
Diagnostics
Dashboard
Logging support
Connection status monitoring
Better backward compatibility
Less work required in client software
Easier future updates
Updating to Inverse Installer 2.0 (From Version 1.0)
This release contains breaking changes.
Changes include:
Official product names replace previous generic names.
Fixed bug where haply-inverse-service interfered with the Touch3DS device.
Added initial query for Inverse3 handedness when first connecting the device.
Added service caching for Inverse3 and VerseGrip state.
Added handedness support for device_open_first.
Added tutorials directly inside the installer.
Fixed crashes caused by overloaded request queues.
Improved error reporting and handling.
Side-by-Side Comparison of the Inverse Installer and the Hardware API
(Comparison table/content follows in the original article.)
The latest changelogs and release notes for all Haply software products are always available on the Haply Developer Hub Releases page.
Our newsletter subscribers saw this first! Join our monthly newsletter for early access to the latest updates and news.
