Hey everyone - sorry for the slow response, had some urgent things to handle on other projects the past few weeks. Calming down now, getting back to The Edgy.
Thanks to everyone using the app, leaving feedback, and those who picked up a Ko-fi pack - it means a lot \o/
Vibration support is my current focus. The plan is to add a vibration channel so The Handy and a vibrator toy can run simultaneously as a first step, which would also cover vibration-only devices. That said, my Intiface tests have been showing inconsistent latency between app commands and my device reaction, so I need to figure out the right approach before shipping something that feels broken. Coming, just not rushing it.
I ran tests with SBS and over-under VR rendering. Not conclusive at all: as soon as the browser enters stereoscopic mode, the headset takes over all native input, so you lose full control of the app. A dedicated VR app would probably be the right approach, but that means Android builds, proper headset compatibility across devices… not a small undertaking. Parked for now.
On the research side, I’ ve started looking at audio-driven behaviors, using beat and energy from a video’s audio track to modulate the device in real time. Main target would be PMV and Cock Hero type content, where you want the device to loosely follow the rhythm without a full funscript.
Also looking at external input support. I was reached out on Reddit by someone running an ESP32 to replicate what the Edge-o-Matic does, at a fraction of the cost. That kind of DIY angle is what pushes me toward thinking generic rather than device-specific: a flexible input interface that can accept multiple sources rather than one-off integrations. Still in analysis phase on both fronts.
A few bug reports I want to address. On the stuttering issue with Handy 2 reported by a few people: I haven’t been able to reproduce it consistently, but the fact that it doesn’t happen with the orgasm button is a useful clue. If you’re affected, can you tell me if it started after a specific version?
On grindy/jerky movements with steep velocity slopes: noted, sounds like an acceleration clamping issue. Does it happen on specific presets or across the board?
On the feature side: button mapping for arousal and profile switching is something I want to revisit (there are already mapped on numpad and arrow key), but a custom mapping is something better. Text input for curve points instead of dragging is a good UX improvement, noted. Per-axis toggle for OSR2/SR6 is another challenge, making the app work with R (vibrato) channel will be the first step.
@jimmyk9 on the multiple videos idea, loading a playlist and having the app transition between videos based on the active behavior is actually interesting. There are real challenges around transitions and performance but I can see the concept: one video per behavior, swapping when the pattern changes. Did you get that idea from another app? Curious what the reference is.
@Stardust07 On the abrupt stop: there is already already transition handling when you move the arousal slider, it smooths the upcoming commands over the next few milliseconds. That said it relies on a stable and fast connection. How would you rate your connection when this happens? On using a funscript to build a behavior profile with its own variations: that’s actually an idea I’ve had in mind too. Good to know there’s interest, I’ll keep it on the radar.
@atxahzen is your device set to double connection mode? So you can easily switch from bluetooth connection to wifi modfe? If yes try to set it into wifi only mode to see if it fix your issue. The problem beyond that is that I didnt receive event for connection lost, so yes, you have to refresh the page… “something pops up behind the current window when i click on the little info circle”, I’ve tried all info circle and didnt see issue, can you tell me which one is it? You’re right about action buttons, they are broken right now they are supposed to control arousal level, I have to take a look on it.
Cock Hero mode is actually a great fit, it’s basically what I use the app for myself. Lovense Domi 2 and vibration-only devices in general will be covered once the vibration channel lands.
Sorry if I’ve missed someone 
, feel free to answer here
.