RN
For roughly sixteen years, the single biggest constraint on internet-connected sex toys was a document filed in 1998.
US Patent 6,368,268 — granted in 2002, covering the interactive control of sexual devices over a computer network — was broad enough to read onto essentially the entire concept. It was acquired and asserted against a string of small manufacturers, among them Comingle, Holland Haptics and Vibease, with a suit filed against LELO in July 2017. The Electronic Frontier Foundation gave it their Stupid Patent of the Month award in July 2015. It expired on 17 August 2018.
Hold that date in mind, because almost everything people find exciting about this category is younger than it. The field did not have a hard engineering decade. It had a legal one.
"Haptic" is doing a lot of work
Start with the vocabulary, because the marketing has outrun the hardware by some distance.
In the research sense, haptics means rendering touch: force feedback that resists your hand, textures your skin can distinguish, the sensation of an edge or a surface. That is a genuinely hard problem and it is not close to solved in any consumer product, in any industry.
What actually ships in this category is narrower and worth naming precisely. There are vibration motors — eccentric rotating masses, or linear resonant actuators with a crisper response. There are mechanical stroking assemblies. There are air-pressure systems producing suction rather than contact. There is heating. Each is an actuator running on a timeline.
That is not nothing, and the better devices are considerably more refined than the ones from a decade ago. But it is actuation, not touch rendering, and articles promising that the next generation will reproduce the feeling of another person are describing a research problem as though it were a product roadmap.
Where the real gains actually came from
The interesting progress has not been in the hardware at all. It has been in synchronisation.
The meaningful innovation is scripting: a timeline of device positions and intensities aligned to a video, so a device moves in time with what is on screen. The community format for this — funscript — is a simple, open, well-understood file, and it is the reason the experience improved noticeably without any actuator getting better. A mediocre device following a well-authored script beats a superior device running a generic pattern, every time.
That same layer is what makes VR material the natural pairing. Not because the headset improves the sensation, but because it removes the competing visual frame, and synchronisation errors that are obvious on a monitor become much less noticeable when the visual field is filled.
The interactive-with-a-partner use case — the one the patent was written about and the one every article leads with — remains the least developed of the three, and mostly for an unglamorous reason: latency and connection reliability are hard, and the experience degrades badly when they slip.
The thing that will actually decide the next decade
There is no standard. That is the whole story.
Every major manufacturer runs its own protocol, its own app, and its own account system. A script authored for one ecosystem does not simply work in another. A device you own is usable with the software its vendor supports and, in the general case, nothing else. If that vendor discontinues the app or shuts down the service, the hardware in your drawer loses most of its function while remaining in perfect working order.
The counterweight is an open-source abstraction layer — the Buttplug protocol and the Intiface software built on it — which exists precisely because manufacturers do not interoperate, and which supports a broad range of devices from a single interface. That such a project is necessary is the clearest statement available about the state of the industry.
If you are buying from the toy retailers, this is the specification worth checking and the one never printed on the box: whether the device works with anything other than its own manufacturer's app.
What leaves the room
The last constraint is the one the future-of-pleasure genre almost never mentions, and it is the one with an actual legal record behind it.
In 2017 Standard Innovation settled a class action concerning its We-Connect app, which paired with its We-Vibe devices. The allegation was that usage data — including when a device was used and at what settings — was transmitted without users' consent. The settlement established funds of roughly $3.75 million, split between a purchaser class and an app class. The company resolved the matter without admitting that its data practices had broken any law.
More recently, Lovense has faced a class action alleging comparable failures to disclose and obtain consent for usage data collection, alongside a 2017 finding concerning audio capture by its app and vulnerabilities reported by security researchers in 2021. The company has since revised its security protocols and privacy policy. These are allegations and researcher findings rather than established misconduct, and should be read that way.
Set the pattern out plainly, though, because it is structural rather than anecdotal. These devices are internet-connected, tied to an app account, and generate a stream of some of the most sensitive behavioural data a person produces. Whether that data leaves the room, where it is stored, and what happens to it if the company is sold are questions with real answers that are rarely published in a form anyone can check.
What would actually have to change
The honest version of a future-of-haptics article is short.
Touch rendering worth the name requires advances in actuator physics and in modelling skin response that no one in this sector is positioned to make; it will arrive here, if it arrives, borrowed from surgical robotics or prosthetics. Remote intimacy at a quality people would use habitually requires latency engineering rather than better motors. Devices outliving their manufacturers requires an interoperability standard the industry has no commercial reason to adopt. And trustworthy devices require a default of local control with no account and no telemetry, which is the opposite of where the subscription-shaped incentives point.
None of that is impossible. But note that only the first item on the list is a hardware problem — and it is the only one every article about this subject talks about.