We like the realtouch and intend to support it on the frixion platform eventually -- it has an open source sdk available and having broad support for diverse haptic experiences is the point of the plugin system -- however the realtouch is different in some important ways compared to what we've accomplished here using robotics.
The realtouch is an "input only" device that sits motionless on a mans lap while the conveyor belts do their job either from an encoded video, or from a live model using a touch sensitive dildo called a joystick. This is flow of telemetry in a single direction -- to the realtouch. Our devices create a tethered sense of physical intimacy and connection. One partner feels whats happening with the other side, and vice versa, simultaneously. Also, our design has all the moving parts on the outside, which we feel is more appealing than sticking your penis into an opaque grinding box. (Our devices are very quiet btw, will be adding new videos next week to demonstrate)
You can imagine when we add support for the realtouch that other devices on the platfrom such as the robot itself and accelerometer products will be able to send telemetry to the device to control its functions, and vice versa, the joystick would be able to send telemetry to the robots to manipulate a fleshlight/tenga/sleeve. It's really a robust api that enables all devices to interact where their functionalities overlap.
However, we should all be supportive of realtouch right now -- it appears they're having licensing issues with a certain patent holder that is turning the screws on them and without intervention they wont be able to continue selling devices next year. Dealing with this minefield of patents and licensing has been an important predicate for our development at frixion, and we are eager to create a "safe haven" for other developers to deploy their devices under the agreements we hold in the future.
The realtouch is an "input only" device that sits motionless on a mans lap while the conveyor belts do their job either from an encoded video, or from a live model using a touch sensitive dildo called a joystick. This is flow of telemetry in a single direction -- to the realtouch. Our devices create a tethered sense of physical intimacy and connection. One partner feels whats happening with the other side, and vice versa, simultaneously. Also, our design has all the moving parts on the outside, which we feel is more appealing than sticking your penis into an opaque grinding box. (Our devices are very quiet btw, will be adding new videos next week to demonstrate)
You can imagine when we add support for the realtouch that other devices on the platfrom such as the robot itself and accelerometer products will be able to send telemetry to the device to control its functions, and vice versa, the joystick would be able to send telemetry to the robots to manipulate a fleshlight/tenga/sleeve. It's really a robust api that enables all devices to interact where their functionalities overlap.
However, we should all be supportive of realtouch right now -- it appears they're having licensing issues with a certain patent holder that is turning the screws on them and without intervention they wont be able to continue selling devices next year. Dealing with this minefield of patents and licensing has been an important predicate for our development at frixion, and we are eager to create a "safe haven" for other developers to deploy their devices under the agreements we hold in the future.