We now have more devices than just Handy, starting with the Oh
Simpler onboarding
We want our devices to be easier to use. Getting online has been a struggle for the a lot of non tech users. With the new Handy Onboarding app and FW4, we hope to simplify this.
Improved server-device communication
We moved from JSON to protobuf
Improved backend
We moved from NodeJs to Go
More use cases
With the new streaming protocol (HSP) we hope that we can expand the use cases of our device.
hello first thank you for continuing to improve the API, practical I have a problem is that the handy does not detect via bluetooth with intiface it is me who unlocks me badly by what I tested for myself train from ((new.handyfeeling.com)) and it works but I want it to detect it from Intiface
Thanks for the continued development! Love the fact that it auto-connects in the v4 firmware and connects faster!
Since it’s beta, giving feedback on what made me roll back to 3.2.3 from the latest versions (including the newest FW4.0.12 straging version.)
When you try to use the old remote control Handyverse with the new v4 firmware, it behaves differently, and not in a good way. The strokes go smaller than what they seem to be set at, and seem to be at a faster rate. So the backwards compatibility, even through it technically works, is doesn’t work as expected. For example, if I have the range set to 40-60, it doesn’t feel like 20% of a stroke, it feels like 5% now. And if I have the speed set to 0, it feels like 15 or so. Presets are missing from the new remote control app which is why I was going back to use the old one. If you end up re-implementing presets with the new firmware, I would love to see them be able to be moved around rather than being stuck with the order they were created.
Beatbox is neat and promising, but would love to see the basics (remote control with presets and random controller) implemented well first, then continue to work on the new features like BeatBox.
Thank you for the feedback! I’ve noted your observations and we’ll take a closer look at the stroke length and speed adjustments.
Regarding presets, we’re working on adding flexible scripting options that would allow for different “positions” to toggle between. The previous presets were primarily simple up-and-down motions with adjustable speed and stroke length—does this match what you’d hope to see in an upgraded presets feature?
Additionally, please note that there’s now an option to store scripts in the Beatbox and easily switch between them.
I did notice you can save the Beatbox stuff which is nice.
I’d like to see basically what you had in the original remote control presets page, but also the ability to organize them. I guess I’m just not that into using scripts that much, because I like controlling it to what I’m in the mood for at that very moment, but controlling it by using the sliders on the remote control on the fly can be distracting. So having presets (pretty much like the concept of the “Wingman” app) is what I would like.
I do like using random control though too, where it can be random within bounds that you set by adjustable parameters. I’d like to see the ability to create (and organize) presets on the random stroker page too. There are 3 unchangeable predefined presets there, tease, blowjob, and deepthroat on the old random stroker page, but I would love to be able to go back and forth between remote control and self created presets all on the fly on the same page.
Here is a screenshot of what my presets look like on the old Remote Control page. I wish I could just add those (and organize them) in the “Presets” section of the “Random Stroker” page and easily go back and forth between those presets and the random stroker smoothly without being distracted.
Nice. I guess it’s time for me to give FW4 another shot.
@rivulets I’d vote for custom presets too. Especially with the “layer” of randomness as funscript.io let’s you apply - shifting node positions vertically and/or vertically by random number from the interval 0 to x. And as usual keyboard controls are low hanging yet delicious fruit.
At the same time I understand the new Beatbox feature can be seen as even more customizable replacement for those simple presets.
I’ve been meaning to upgrade to API v2 for a long time now but never got around testing/finishing it.
Would v2 still be a good option to make sure I support FW3+FW4 simultaneously or should I just go straight for v3? (will v3 be backwards compatible with FW3?)
Yeah, I think both would be great. I didn’t think the development of the old remote control page with customizable (and arrange-able) presets on the remote page would be too difficult to implement, but hard to say without being a developer and being familiar the the underlying technical details and possible limitations. And unifying the remote stroker page with the remote control page would be a win, at least to me and the way I like to use them. I didn’t quite understand why the old version gave you those 3 canned presets on the remote stroker page without the ability to create your own without going back to the remote control page. I also didn’t understand why you couldn’t arrange the presets on the remote control page, since both do not seem like a lot of development work. Combining all of that onto one page would be the most ideal to me.
I have made BeatBox scripts, and I do find it enjoyable at times, but in the end, I go back to the customizable presets and random stroker functions of the old site. Also found https://funscript.io as a good change of pace too, but I have still desired what I have described above.
Hi! I recommend going straight to API v3. It includes new features and improved support. While API v3 is exclusive to FW4, we’re rolling it out to more Handy users, and future hardware will only support FW4.
Thanks for the feedback! I’ve created a ticket for this feature request for when we have free time. Note: the new HandyFeeling website includes some keyboard controls.
Tried the 4.0.12 for the beatbox and the keyboard controls for adjusting strokes and offset. Thanks again for so quick implementation @handyAlexander.
Found 1-2 minor bugs there though:
When setting offset by keyboard you can’t get back to 0. My step is 5 and it just jumps from +5 to -5 and back.
Kinda nitpicking here, but controls can be mapped only to alphanumerical keys. While I understand you can’t really allow users to map to special keys with either browser or system-wide function, I don’t see why e.g. “-” or “+” can’t be used.
Thanks. Would you mind adding the suggestions to our new “suggestions” tool? https://suggestions.handyfeeling.com/ . With this tool it will be easier us to sort the incoming requests.
Tried FW4 again and I think it moves better now. But as you wrote before the movement is more mechanical now compared to FW3, less smooth. Is this by design or do you plan to correct it?
The motion in FW4 is more “correct” compared to FW3. I’m not sure it would be wise to introduce smoothing on the firmware side. It might be better to focus on refining the scripts themselves, as most of them currently rely on mechanical movements with only top and bottom points defined.
Vitor helped you out by providing an initial suggestion as a starting point, so hopefully, future suggestions will follow the same “template”. Feel free to add more suggestions here:-)
